Method and system for integrating discrete invoices into a personal financial management and bill payment system and then aggregating discrete invoices having the same payee business into a single payment transfer transaction

ABSTRACT

Invoice related financial transaction data is obtained and integrated into a personal financial management and bill payment system. Then all requested invoice payments associated with invoices represented in the invoice related financial transaction data having the same payee business are identified and collected into aggregated first payee business invoice payment request related financial transaction data. The aggregated first payee business invoice payment request related financial transaction data is then analyzed to determine the aggregated total amount owed to the payee business and this aggregated total amount is processed as a single funds transfer item by the personal financial management and bill payment system.

RELATED APPLICATIONS/INCORPORATION BY REFERENCE

This application is related to U.S. patent application Ser. No.15/140,117 (docket number INTU169676), filed on behalf of the sameInventors of the present patent application, filed on Apr. 27, 2016,entitled “METHOD AND SYSTEM FOR PROVIDING INVOICES GENERATED THROUGH ABUSINESS INVOICING SYSTEM TO A CUSTOMER USER OF A PERSONAL FINANCIALMANAGEMENT AND BILL PAYMENT SYSTEM,” which is herein incorporated byreference in its entirety as if it were fully set forth herein.

This application is also related to U.S. patent application Ser. No.15/140,131 (docket number INTU169677), filed on behalf of the sameInventors of the present patent application, filed on Apr. 27, 2016,entitled “METHOD AND SYSTEM FOR IDENTIFYING INVOICES THAT ARE PAIDTHROUGH A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM,” whichis herein incorporated by reference in its entirety as if it were fullyset forth herein.

This application is also related to U.S. patent application Ser. No.15/142,708 (docket number INTU169678), filed on behalf of the sameInventors of the present patent application, filed on Apr. 29, 2016,entitled “METHOD AND SYSTEM FOR INTEGRATING BUSINESS INVOICES INTO APERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM,” which is hereinincorporated by reference in its entirety as if it were fully set forthherein.

BACKGROUND

Currently, several personal financial management and bill paymentsystems are available to help a personal financial management and billpayment system user, or any authorized party acting on behalf of apersonal financial management and bill payment system user, obtainfinancial transaction data representing financial transactions conductedby the user, process/analyze the financial transaction data, displaycategorized financial transaction data, generate financial transactionreports, generate bills due and payment due reports, and/or make manual,semi-automated, and/or automatic bill payments through the personalfinancial management and bill payment system.

Some personal financial management and bill payment systems help usersmanage their finances and/or track their expenditures/financialtransactions by providing a centralized interface with banks, creditcard companies, and various other financial institutions, forelectronically identifying and categorizing the user's financialtransaction data. Currently, personal financial management and billpayment systems typically obtain electronic financial transaction data,such as payee data, payment amount data, transaction date data, etc. viacommunication with banks, credit card providers, or other financialinstitutions, using electronic data transfer systems, or various othersystems for obtaining/transferring financial transaction data.

Personal financial management and bill payment systems have proven to bevery popular and valuable tools for the users of the personal financialmanagement and bill payment systems. This is largely due to the factthat using a personal financial management and bill payment system, auser can obtain most, if not all, of their financial transaction datafrom multiple sources and this data can be processed and analyzed in itsentirety to create in depth, and very complete reports and features.Some personal financial management and bill payment systems include apayment due report/display generation feature. Typically, a payment duereport includes personal financial management and bill payment systempayment due data representing a listing of payments due, e.g., billpayment due items, within a defined period of time, such as a month,which require the user's attention.

In some cases, the user of the personal financial management and billpayment system is also provided the capability to make the listedpayments on a manual, semi-automatic, i.e., with user approval, orautomatic, basis.

Users of personal financial management and bill payment systems havecome to rely on these payment due reports and often use the reports, andpayment features, to pay the vast majority of their bills through thepersonal financial management and bill payment system. However, thereremain several issues that are associated with currently availablepersonal financial management and bill payment systems.

First, currently available personal financial management and billpayment systems do not provide a mechanism for automaticallyidentifying, or distinguishing, invoices, invoice related financialtransaction data, and/or invoice payments from bill payment data andthen properly processing and integrating identified invoice relatedfinancial transaction data into the personal financial management andbill payment system as an invoice related payment due items.

As used herein, the term “bill” includes, but is not limited to, anaccount statement or other potentially recurring cost and financialtransaction. Currently, bill payments due are represented in personalfinancial management and bill payment system payment due data. Examplesof bills include, but are not limited to: rent payments, utilitypayments, credit card payments, grocery store payments, vehicle costs,etc. Bills are typically associated with larger, well known, and/ornationally or regionally known, payee businesses.

In contrast to the term “bill”, herein the term “invoice” includes, butis not limited to, documents/data associated with a specific productand/or service provided by a business and for which full payment istypically requested via a discrete invoice statement. Herein the term“invoice related financial transaction data” includes data representingall, or part of, an “invoice.” A given discrete invoice is thereforetypically a non-recurring expense and/or is associated with specificproducts and/or services rendered, even though multiple, and evenrecurring identical, invoices can be generated by the same payeebusiness for the same payor customer if multiple products and/orservices, and/or the same products and/or services, are provided.Invoices are typically associated with smaller, regional or local, payeebusinesses than those associated with bills.

Herein the terms “payment,” and/or “payment due,” and/or “payment dueitems” are used interchangeably and include any payment owed by a firstparty, i.e., payor party, to a second party, i.e., a payee party.Consequently, as used herein, the terms “payment” and/or “payment due”include both “bills” and “invoices.”

One side effect of the popularity of payment due reports and the billpayment features offered through some personal financial management andbill payment systems is that any payment due items not included in thepayment due reports, and/or not capable of being paid through the billpayment feature of the personal financial management and bill paymentsystems, are often forgotten, or at least treated as secondary, by theusers of the personal financial management and bill payment systems. Inshort, as users of personal financial management and bill paymentsystems come to rely on the payment due reports listing payment dueitems and the bill payment features offered through some personalfinancial management and bill payment systems, they may forget, orneglect, any payments, such as invoice payments, that are not includedin the payment due reports and payment due item listings and/or can't bepaid through a bill payment feature of currently available personalfinancial management and bill payment systems.

This represents a significant and long standing technical problem in thefinancial management system, payment processing, and invoicing arts.This is because currently available personal financial management andbill payment systems process financial transaction data and generatepersonal financial management and bill payment system payment due datalargely associated with recurring payments and/or revolving accounts,i.e., bills, such as credit card accounts, that can be identifiedthrough analysis of the users' financial transaction data history. Inparticular, currently available personal financial management and billpayment systems only identify recurring bills for inclusion in personalfinancial management and bill payment system payment due data and thepayment due item listings of payment due reports, and/or other remindersof payments due, that are ultimately provided to the users of thepersonal financial management and bill payment systems. As a result,currently, one time only payments due, or non-revolving accounts, suchas invoices, are almost never identified or included in the personalfinancial management and bill payment system payment due data and/orpayment due item listings of payment due reports generated by personalfinancial management and bill payment systems.

As a result of the situation described above, smaller, local orregional, businesses generating invoices for their customers mustcurrently rely on delivering their invoices to the customers throughsecondary, i.e., non-personal financial management and bill paymentsystems, mechanisms, and/or processes, such as e-mail or postal service.This, in turn, often leads to a situation where the invoicing businesshas trouble getting invoices in front of their customers, and/or gettingtheir customers' attention, and/or integrating their invoices into thecustomers' payment routine, and/or getting paid. This situation existstoday despite the fact that most businesses are business users ofsophisticated business invoicing systems and/or business financialmanagement systems that include business invoicing features.

Consequently, there is a long standing technical problem in thefinancial management system, payment processing, and invoicing arts inthat businesses are currently unable to access personal financialmanagement and bill payment systems used by their customers and provideinvoices to their customers through the personal financial managementand bill payment systems used by their customers as invoice relatedpayment due items.

In addition, currently, when invoice related financial transaction datais entered manually by users of bill payment features offered through apersonal financial management and bill payment system, that is, bysimply entering payee data, amount data, routing data, and payment datedata, a given payment is typically not identified as a paymentassociated with an invoice, as opposed a bill. In addition, financialtransaction data obtained by, or through, a personal financialmanagement and bill payment system often includes financial transactiondata representing financial transactions performed by, or on behalf, ofa user through another entity such as another financial institutionaccount. Often, this financial transaction data also fails to indicatewhether a given payment is associated with a bill or with an invoice.

Consequently, users of personal financial management and bill paymentsystems can pay either bills or invoices without designating which typeof payment is being made. This is unfortunate given the differencesbetween “bills” and “invoices.” in terms of how these two types ofpayments should ideally be identified, categorized, and processed by thepersonal financial management and bill payment system. In short, itwould be very beneficial to identify any invoices and, once identified,provide a feature whereby identified invoices generated by a businessinvoicing system, and/or one or more financial institutions providingfinancial transaction data to the personal financial management and billpayment system, could be identified and then properly processed andintegrated into the personal financial management and bill paymentsystem as an invoice payment due item.

As a result there is also a long standing technical problem in thefinancial management system, payment processing, and invoicing arts inthat currently available personal financial management and bill paymentsystems do not provide a mechanism for automatically identifying, ordistinguishing, invoices, invoice data, and/or invoice payments and thenproperly processing and integrating identified invoices into a personalfinancial management and bill payment system as an invoice relatedpayment due item.

Another issue associated with currently available personal financialmanagement and bill payment systems is that each time a discretetransfer of funds is made, i.e., a funds transfer transaction isconducted, by, or through, a personal financial management and billpayment system, a funds transfer fee is typically charged by a financialinstitution providing the funds and/or the provider of the personalfinancial management and bill payment system. This funds transfer fee istypically charged to the payor business receiving the funds as paymentfrom a payee user of the personal financial management and bill paymentsystem, and/or the payee user of the personal financial management andbill payment system providing payment to the payor business, and/or thepersonal financial management and bill payment system facilitating thefunds transfer from the payee user of the personal financial managementand bill payment system to the payor business. Consequently, it ishighly desirable that the number of funds transfer transactionsconducted through the personal financial management and bill paymentsystem be minimized for all parties involved.

However, since businesses are currently unable to access personalfinancial management and bill payment systems used by their customersand provide invoices to their customers through the personal financialmanagement and bill payment systems used by their customers as paymentdue items, and currently available personal financial management andbill payment systems do not provide a mechanism for automaticallyidentifying, or distinguishing, invoices, invoice related financialtransaction data, and/or invoice payments or properly processing andintegrating invoices into a personal financial management and billpayment system as an invoice related payment due item, invoices areeither paid individually by mechanisms outside the personal financialmanagement and bill payment system or, even if the invoice relatedfinancial transaction data is manually entered, or otherwise providedto/obtained by, the personal financial management and bill paymentsystem, each discrete invoice is presented as a discrete payment due,and is paid individually, even when multiple invoices are directed tothe same payor user by the same payee business. Consequently, currently,a discrete invoice payment funds transfer is made, and therefore adiscrete invoice payment funds transfer charge is incurred, each time aninvoice payment is made from a discrete payor user of the personalfinancial management and bill payment system to a given payee business,even when each of the discrete invoice payments are made to the samegiven payee business and, in some cases, even when each of the discreteinvoice payments is made to the same given payee business by the samepayor user of the personal financial management and bill payment system.

As a result, currently, numerous funds transfer charges are incurred inthe form of discrete invoice payment funds transfer charges associatedwith invoice payments made to the same payee business through personalfinancial management and bill payment systems. This clearly representsan inefficient use of resources and a significant, largely unnecessary,cost to the parties involved

In addition, since currently, each invoice payment made from a discretepayor user of the personal financial management and bill payment systemto a given payee business is processed as an individual and discretefunds transfer transaction, even when each of the discrete invoicepayments are made to the same given payee business and, in some cases,even when each of the discrete invoice payments is made to the samegiven payee business by the same payor user of the personal financialmanagement and bill payment system, human and non-human resources,processing power and processor cycles, memory, and communicationsbandwidth are inefficiently utilized to process numerous discrete fundstransfers representing invoice payments made to the same given payeebusiness by multiple payor users of a personal financial management andbill payment system. This also clearly represents an inefficientallocation of resources.

Consequently, there is a long standing technical problem in the paymentprocessing, invoice processing and financial management arts ofproviding for automatic integration of invoice related financialtransaction data into a personal financial management and bill paymentsystem and/or identifying, or distinguishing, invoice related financialtransaction data, and then aggregating requested invoice payment amountsassociated with invoices having the same payee business into a singlefunds transfer transaction item to be processed by the personalfinancial management and bill payment system.

What is needed is a method and system for automatically integratinginvoice related financial transaction data into a personal financialmanagement and bill payment system, and/or identifying, ordistinguishing, invoice related financial transaction data, and thenaggregating requested invoice payment amounts associated with invoicesrepresented in the invoice related financial transaction data having thesame payee business into a single funds transfer transaction item to beprocessed by the personal financial management and bill payment system.In this way, invoices represented in invoice related financialtransaction data could be processed by the personal financial managementand bill payment system at minimal cost to the parties involved, usingminimal resources, and in a seamless and effective manner.

SUMMARY

In accordance with one embodiment, invoice related financial transactiondata is obtained and integrated into a personal financial management andbill payment system. Then, all requested invoice payments associatedwith invoices represented in the invoice related financial transactiondata having the same payee business are identified and aggregated.

In one embodiment, the amounts of the aggregated requested invoicepayments for the payee business are then summed to determine the totalamount to be transferred to the payee business and this total amount tobe transferred to the payee business is then processed as a single fundstransfer item by the personal financial management and bill paymentsystem.

Consequently, using the disclosed embodiments, invoices represented ininvoice related financial transaction data can be integrated into, andprocessed by, the personal financial management and bill payment systemat minimal cost to the parties involved, using minimal resources, and ina seamless and effective manner.

Therefore, the disclosed embodiments provide an efficient, effective,and highly adaptable solution to the long standing technical problem inthe bill payment, invoice processing, and financial management arts ofautomatically integrating invoice related financial transaction datainto a personal financial management and bill payment system, and/oridentifying, or distinguishing, invoice related financial transactiondata, and then aggregating requested invoice payment amounts associatedwith invoices represented in the invoice related financial transactiondata having the same payee business into a single funds transfertransaction item to be processed by the personal financial managementand bill payment system.

In accordance with one embodiment of a method and system for integratingdiscrete invoices into a personal financial management and bill paymentsystem and then aggregating discrete invoices having the same payeebusiness into a single funds transfer transaction, access to invoicerelated financial transaction data generated by the one or more payeebusinesses is obtained.

In one embodiment, the invoice related financial transaction datarepresents two or more discrete invoices submitted by one or more payeebusinesses requesting payment by one or more payor users of the personalfinancial management and bill payment system.

In one embodiment, the invoice related financial transaction dataincludes payee business identity data associated with each discreteinvoice represented in the invoice related financial transaction data.In one embodiment, the payee business identity data represents theidentity of the payee business associated with each discrete invoicerepresented in the invoice related financial transaction data.

In one embodiment, the invoice related financial transaction data alsoincludes payor user identity data associated with each discrete invoicerepresented in the invoice related financial transaction data. In oneembodiment, the payor user identity data represents the identity of thepayor user associated with each discrete invoice represented in theinvoice related financial transaction data.

In one embodiment, the invoice related financial transaction datafurther includes invoice amount data associated with each discreteinvoice represented in the invoice related financial transaction data.In one embodiment, the invoice amount data represents the payment amountassociated with each discrete invoice represented in the invoice relatedfinancial transaction data.

In accordance with one embodiment, the invoice related financialtransaction data is integrated into personal financial management andbill payment system payment due data associated with a personalfinancial management and bill payment system. In one embodiment, thepersonal financial management and bill payment system payment due datarepresents one or more payments due associated with one or more users ofthe personal financial management and bill payment system as payment dueitems to be paid through the personal financial management and billpayment system.

In accordance with one embodiment, invoice payment request data isreceived from one or more users of the personal financial management andbill payment system. In one embodiment, the invoice payment request datarepresents one or more requests from one or more users of the personalfinancial management and bill payment system to pay one or morerequested invoice payment amounts associated with one or more discreteinvoice payment request related invoices represented in the invoicerelated financial transaction data through the personal financialmanagement and bill payment system.

In accordance with one embodiment, access to the personal financialmanagement and bill payment system and the personal financial managementand bill payment system payment due data, including the integratedinvoice related financial transaction data, and the invoice paymentrequest data is obtained.

In accordance with one embodiment, the invoice payment request data isanalyzed to identify discrete invoice payment request related invoicedata representing one or more discrete invoice payment request relatedinvoices represented in the invoice related financial transaction data.

In accordance with one embodiment, the integrated invoice relatedfinancial transaction data associated with the discrete invoice paymentrequest related invoices is analyzed to identify the payee businessidentity data associated with each discrete invoice payment requestrelated invoice represented in the discrete invoice payment requestrelated invoice data.

In accordance with one embodiment, a first payee business represented inthe payee business identity data associated with two or more discretefirst payee business invoice payment request related invoicesrepresented in the discrete invoice payment request related invoice datais identified.

In accordance with one embodiment, all the invoice related financialtransaction data associated with the two or more discrete invoicepayment request related invoices is aggregated to generate aggregatedfirst payee business invoice payment request invoice data.

In accordance with one embodiment, the aggregated first payee businessinvoice payment request invoice data is analyzed to identify therequested invoice payment amount data associated with each of the two ormore discrete invoice payment request related invoices.

In accordance with one embodiment, the requested invoice payment amountdata associated with each of the two or more discrete invoice paymentrequest related invoices is processed and summed to generate aggregatedtotal first payee business invoice payment amount data representing atotal requested invoice payment amount for the first payee business asrequested by two or more users of the personal financial management andbill payment system.

In accordance with one embodiment, the aggregated total first payeebusiness invoice payment amount data is then processed as a single firstpayee business funds transfer item using the personal financialmanagement and bill payment system.

The disclosed embodiments provide an efficient, effective, and highlyadaptable solution to the long standing technical problem in the billpayment, invoice processing, and financial management arts ofautomatically integrating invoice related financial transaction datainto a personal financial management and bill payment system, and/oridentifying, or distinguishing, invoice related financial transactiondata, and then aggregating requested invoice payment amounts associatedwith invoices represented in the invoice related financial transactiondata having the same payee business into a single funds transfertransaction item to be processed by the personal financial managementand bill payment system.

However, the disclosed method and system for integrating discreteinvoices into a personal financial management and bill payment systemand then aggregating discrete invoices having the same payee businessinto a single funds transfer transaction does not encompass, embody, orpreclude other forms of innovation in the area of automated financialtransaction bill payment processing and invoicing. In addition, thedisclosed method and system for integrating discrete invoices into apersonal financial management and bill payment system and thenaggregating discrete invoices having the same payee business into asingle funds transfer transaction is not related to any fundamentaleconomic practice, fundamental data processing practice, mental steps,or pen and paper based solution. In fact, the disclosed embodiments aredirected to providing solutions to the relatively new problemsassociated with the automatic processing and display of electronicfinancial transaction data obtained from multiple sources, makingelectronic bill payments, and the management and processing of largeamounts of data, i.e., “big data.” Consequently, the disclosed methodand system for integrating discrete invoices into a personal financialmanagement and bill payment system and then aggregating discreteinvoices having the same payee business into a single funds transfertransaction is not directed to, does not encompass, and is not merely,an abstract idea or concept.

In addition, the disclosed method and system for integrating discreteinvoices into a personal financial management and bill payment systemand then aggregating discrete invoices having the same payee businessinto a single funds transfer transaction provides for significantimprovements to the technical fields of electronic transaction dataprocessing, invoicing, financial transaction categorization, informationdissemination, data processing, data management, data filtering andmining, automatic electronic bill payment, and user experience.

In addition, by allowing for the integration of invoices and invoicedata into a personal financial management and bill payment system, thedisclosed method and system for integrating discrete invoices into apersonal financial management and bill payment system and thenaggregating discrete invoices having the same payee business into asingle funds transfer transaction helps users of the personal financialmanagement and bill payment system identify and pay their invoices.This, in turn, helps avoid the reissuance and repeated transmission ofpayment due reminders and for the entry, processing, and dissemination,of redundant invoice data; thereby eliminating unnecessary data analysisbefore resources are allocated to processing, and/or correcting,redundant reminder data and the redundant reminder data is furthertransmitted/distributed.

Consequently, using the disclosed method and system for integratingdiscrete invoices into a personal financial management and bill paymentsystem and then aggregating discrete invoices having the same payeebusiness into a single funds transfer transaction results in moreefficient use of human and non-human resources, fewer processor cyclesbeing utilized, reduced memory utilization, and less communicationsbandwidth being utilized to relay data to, and from, backend systems andclient systems.

As a result, computing systems are transformed into faster, moreefficient, and more effective computing systems by implementing themethod and system for integrating discrete invoices into a personalfinancial management and bill payment system and then aggregatingdiscrete invoices having the same payee business into a single fundstransfer transaction.

In addition, the disclosed method and system for integrating discreteinvoices into a personal financial management and bill payment systemand then aggregating discrete invoices having the same payee businessinto a single funds transfer transaction provides for the entry,processing, and dissemination, of only relevant portions of data;thereby eliminating unnecessary data analysis and correction beforeresources are allocated to processing, and/or correcting,faulty/irrelevant data, and/or the faulty/irrelevant data is furthertransmitted/distributed.

In addition, by aggregating requested invoice payment amounts associatedwith multiple invoices represented in the invoice related financialtransaction data having the same payee business into single fundstransfer item, the disclosed method and system for integrating discreteinvoices into a personal financial management and bill payment systemand then aggregating discrete invoices having the same payee businessinto a single funds transfer transaction provides for the processing anddissemination of invoice related financial transaction data representingmultiple discrete invoices as a single funds transfer entity/object.This, in turn, helps avoid the processing and transmission of multipleindividual invoice payment related data sets and related funds transfertransaction data sets.

Consequently, using the disclosed method and system for integratingdiscrete invoices into a personal financial management and bill paymentsystem and then aggregating discrete invoices having the same payeebusiness into a single funds transfer transaction results in moreefficient use of human and non-human resources, fewer processor cyclesbeing utilized, reduced memory utilization, and less communicationsbandwidth being utilized to relay data to, and from, backend systems andclient systems.

As a result, computing systems are transformed into faster, moreefficient, and more effective computing systems by implementing themethod and system for integrating discrete invoices into a personalfinancial management and bill payment system and then aggregatingdiscrete invoices having the same payee business into a single fundstransfer transaction.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a high level functionality-based block diagram of a hardwareand production environment for integrating discrete invoices into apersonal financial management and bill payment system and thenaggregating discrete invoices having the same payee business into asingle funds transfer transaction, in accordance with one embodiment;and

FIG. 2 is a flow chart representing one example of a generalized processfor integrating discrete invoices into a personal financial managementand bill payment system and then aggregating discrete invoices havingthe same payee business into a single funds transfer transaction, inaccordance with one embodiment.

Common reference numerals are used throughout the FIG.s and the detaileddescription to indicate like elements. One skilled in the art willreadily recognize that the above FIG.s are examples and that otherarchitectures, modes of operation, orders of operation, andelements/functions can be provided and implemented without departingfrom the characteristics and features of the invention, as set forth inthe claims.

Term Definitions

Herein, the term “personal financial management and bill payment system”includes, but is not limited to, the following: computing system,desktop system, mobile system, and/or wearable device implemented,and/or online, and/or web-based, storage based, persistence based,personal financial transaction aggregation and/or processing systems,services, packages, programs, modules, or applications; computingsystem, desktop system, mobile system, and/or wearable deviceimplemented, and/or online, and/or web-based, storage based, persistencebased, personal financial management and budgeting systems, services,packages, programs, modules, or applications; computing system, desktopsystem, mobile system, and/or wearable device implemented, and/oronline, and/or web-based, storage based, persistence based, personaldata management systems, services, packages, programs, modules, orapplications; computing system, desktop system, mobile system, and/orwearable device implemented, and/or online, and/or web-based, storagebased, persistence based, personal accounting systems, services,packages, programs, modules, or applications; personal electronic taxpreparation systems, services, packages, programs, modules, orapplications; and various other personal electronic data managementsystems, services, packages, programs, modules, or applications, whetherknown at the time of filling, or as developed later.

Specific examples of personal financial management and bill paymentsystems include, but are not limited to the following: Mint™, availablefrom Intuit, Inc. of Mountain View, Calif.; Mint Online™, available fromIntuit, Inc. of Mountain View, Calif.; TurboTax™ available from Intuit,Inc. of Mountain View, Calif.; TurboTax Online™ available from Intuit,Inc. of Mountain View, Calif.; and/or various other software systemsdiscussed herein, and/or known to those of skill in the art at the timeof filing, and/or as developed after the time of filing.

Herein, the term “business invoicing system” includes, but is notlimited to, any system through which a business can generate, and/orsubmit, and/or process invoices requesting payment for products and/orservices provided by the business to customers of the business.Therefore, the term “business invoicing system” includes, but is notlimited to, the following: computing system, desktop system, mobilesystem, and/or wearable device implemented, and/or online, and/orweb-based, storage based, persistence based, business accounting and/orinvoicing systems, services, packages, programs, modules, orapplications; computing system, desktop system, mobile system, and/orwearable device implemented, and/or online, and/or web-based, storagebased, persistence based, business financial transaction aggregationand/or processing systems, services, packages, programs, modules, orapplications; computing system, desktop system, mobile system, and/orwearable device implemented, and/or online, and/or web-based, storagebased, persistence based, business financial management and budgetingsystems, services, packages, programs, modules, or applications;computing system, desktop system, mobile system, and/or wearable deviceimplemented, and/or online, and/or web-based, storage based, persistencebased, business management systems, services, packages, programs,modules, or applications; business electronic tax preparation systems,services, packages, programs, modules, or applications; and variousother business electronic data management systems, services, packages,programs, modules, or applications, whether known at the time offilling, or as developed later.

Specific examples of “business invoicing systems” include, but are notlimited to, the following: QuickBooks™, available from Intuit, Inc. ofMountain View, Calif.; QuickBooks Online™, available from Intuit, Inc.of Mountain View, Calif.; QuickBooks Self-Employed™, available fromIntuit, Inc. of Mountain View, Calif.; TurboTax™ available from Intuit,Inc. of Mountain View, Calif.; TurboTax Online™ available from Intuit,Inc. of Mountain View, Calif.; and/or various other software systemsdiscussed herein, and/or known to those of skill in the art at the timeof filing, and/or as developed after the time of filing.

Herein, the terms “software system” and “software application” are usedinterchangeably and can be, but are not limited to, any data managementsystem implemented on a computing system, accessed through one or moreservers, accessed through a network, accessed through a cloud, and/orprovided through any system or by any mechanism and/or process, asdiscussed herein, and/or as known in the art at the time of filing,and/or as developed after the time of filing, that gathers/obtains data,from one or more sources and/or has the capability to analyze at leastpart of the data.

As used herein, the terms “computing system,” “computing device,” and“computing entity,” include, but are not limited to, the following: aserver computing system; a workstation; a desktop computing system; amobile computing system, including, but not limited to, smart phones,portable devices, and/or devices worn or carried by a user; a databasesystem or storage cluster; a virtual asset; a switching system; arouter; any hardware system; any communications system; any form ofproxy system; a gateway system; a firewall system; a load balancingsystem; or any device, subsystem, or mechanism that includes componentsthat can execute all, or part, of any one of the processes and/oroperations as described herein.

In addition, as used herein, the terms “computing system” and “computingentity,” can denote, but are not limited to the following: systems madeup of multiple virtual assets, server computing systems, workstations,desktop computing systems, mobile computing systems, database systems orstorage clusters, switching systems, routers, hardware systems,communications systems, proxy systems, gateway systems, firewallsystems, load balancing systems, or any devices that can be used toperform the processes and/or operations as described herein.

Herein, the terms “mobile computing system” and “mobile device” are usedinterchangeably and include, but are not limited to the following: asmart phone; a cellular phone; a digital wireless telephone; a tabletcomputing system; a notebook computing system; any portable computingsystem; a two-way pager; a Personal Digital Assistant (PDA); a mediaplayer; an Internet appliance; devices worn or carried by a user; or anyother movable/mobile device and/or computing system that includescomponents that can execute all, or part, of any one of the processesand/or operations as described herein.

Herein, the term “production environment” includes the variouscomponents, or assets, used to deploy, implement, access, and use, agiven software system as that software system is intended to be used. Invarious embodiments, production environments include multiple computingsystems and/or assets that are combined, communicatively coupled,virtually and/or physically connected, and/or associated with oneanother, to provide the production environment implementing theapplication.

As specific illustrative examples, the assets making up a givenproduction environment can include, but are not limited to, thefollowing: one or more computing environments used to implement at leastpart of the software system in the production environment such as a datacenter, a cloud computing environment, a dedicated hosting environment,and/or one or more other computing environments in which one or moreassets used by the application in the production environment areimplemented; one or more computing systems or computing entities used toimplement at least part of the software system in the productionenvironment; one or more virtual assets used to implement at least partof the software system in the production environment; one or moresupervisory or control systems, such as hypervisors, or other monitoringand management systems used to monitor and control assets and/orcomponents of the production environment; one or more communicationschannels for sending and receiving data used to implement at least partof the software system in the production environment; one or more accesscontrol systems for limiting access to various components of theproduction environment, such as firewalls and gateways; one or moretraffic and/or routing systems used to direct, control, and/or bufferdata traffic to components of the production environment, such asrouters and switches; one or more communications endpoint proxy systemsused to buffer, process, and/or direct data traffic, such as loadbalancers or buffers; one or more secure communication protocols and/orendpoints used to encrypt/decrypt data, such as Secure Sockets Layer(SSL) protocols, used to implement at least part of the software systemin the production environment; one or more databases used to store datain the production environment; one or more internal or external servicesused to implement at least part of the software system in the productionenvironment; one or more backend systems, such as backend servers orother hardware used to process data and implement at least part of thesoftware system in the production environment; one or more softwaremodules/functions used to implement at least part of the software systemin the production environment; and/or any other assets/components makingup an actual production environment in which at least part of thesoftware system is deployed, implemented, accessed, and run, e.g.,operated, as discussed herein, and/or as known in the art at the time offiling, and/or as developed after the time of filing.

As used herein, the term “computing environment” includes, but is notlimited to, a logical or physical grouping of connected or networkedcomputing systems and/or virtual assets using the same infrastructureand systems such as, but not limited to, hardware systems, softwaresystems, and networking/communications systems. Typically, computingenvironments are either known, “trusted” environments or unknown,“untrusted” environments. Typically, trusted computing environments arethose where the assets, infrastructure, communication and networkingsystems, and security systems associated with the computing systemsand/or virtual assets making up the trusted computing environment, areeither under the control of, or known to, a party.

In various embodiments, each computing environment includes allocatedassets and virtual assets associated with, and controlled or used tocreate, and/or deploy, and/or operate at least part of the softwaresystem.

In various embodiments, one or more cloud computing environments areused to create, and/or deploy, and/or operate at least part of thesoftware system that can be any form of cloud computing environment,such as, but not limited to, a public cloud; a private cloud; a virtualprivate network (VPN); a subnet; a Virtual Private Cloud (VPC); asub-net or any security/communications grouping; or any othercloud-based infrastructure, sub-structure, or architecture, as discussedherein, and/or as known in the art at the time of filing, and/or asdeveloped after the time of filing.

In many cases, a given software system or service may utilize, andinterface with, multiple cloud computing environments, such as multipleVPCs, in the course of being created, and/or deployed, and/or operated.

As used herein, the term “virtual asset” includes any virtualized entityor resource, and/or virtualized part of an actual, or “bare metal”entity. In various embodiments, the virtual assets can be, but are notlimited to, the following: virtual machines, virtual servers, andinstances implemented in a cloud computing environment; databasesassociated with a cloud computing environment, and/or implemented in acloud computing environment; services associated with, and/or deliveredthrough, a cloud computing environment; communications systems usedwith, part of, or provided through a cloud computing environment; and/orany other virtualized assets and/or sub-systems of “bare metal” physicaldevices such as mobile devices, remote sensors, laptops, desktops,point-of-sale devices, etc., located within a data center, within acloud computing environment, and/or any other physical or logicallocation, as discussed herein, and/or as known/available in the art atthe time of filing, and/or as developed/made available after the time offiling.

In various embodiments, any, or all, of the assets making up a givenproduction environment discussed herein, and/or as known in the art atthe time of filing, and/or as developed after the time of filing can beimplemented as one or more virtual assets.

In one embodiment, two or more assets, such as computing systems and/orvirtual assets, and/or two or more computing environments are connectedby one or more communications channels including but not limited to,Secure Sockets Layer (SSL) communications channels and various othersecure communications channels, and/or distributed computing systemnetworks, such as, but not limited to the following: a public cloud; aprivate cloud; a virtual private network (VPN); a subnet; any generalnetwork, communications network, or general network/communicationsnetwork system; a combination of different network types; a publicnetwork; a private network; a satellite network; a cable network; or anyother network capable of allowing communication between two or moreassets, computing systems, and/or virtual assets, as discussed herein,and/or available or known at the time of filing, and/or as developedafter the time of filing.

As used herein, the term “network” includes, but is not limited to, anynetwork or network system such as, but not limited to, the following: apeer-to-peer network; a hybrid peer-to-peer network; a Local AreaNetwork (LAN); a Wide Area Network (WAN); a public network, such as theInternet; a private network; a cellular network; any general network,communications network, or general network/communications networksystem; a wireless network; a wired network; a wireless and wiredcombination network; a satellite network; a cable network; anycombination of different network types; or any other system capable ofallowing communication between two or more assets, virtual assets,and/or computing systems, whether available or known at the time offiling or as later developed.

Herein, the term “party,” “user,” “user consumer,” and “customer” areused interchangeably to denote any party and/or entity that interfaceswith, and/or to whom information is provided by, the method and systemfor integrating discrete invoices into a personal financial managementand bill payment system and then aggregating discrete invoices havingthe same payee business into a single funds transfer transactiondescribed herein, and/or a person and/or entity that interfaces with,and/or to whom information is provided by, the method and system forintegrating discrete invoices into a personal financial management andbill payment system and then aggregating discrete invoices having thesame payee business into a single funds transfer transaction describedherein, and/or a legal guardian of person and/or entity that interfaceswith, and/or to whom information is provided by, the method and systemfor integrating discrete invoices into a personal financial managementand bill payment system and then aggregating discrete invoices havingthe same payee business into a single funds transfer transactiondescribed herein, and/or an authorized agent of any party and/or personand/or entity that interfaces with, and/or to whom information isprovided by, the method and system for integrating discrete invoicesinto a personal financial management and bill payment system and thenaggregating discrete invoices having the same payee business into asingle funds transfer transaction described herein. For instance, invarious embodiments, a user can be, but is not limited to, a person, acommercial entity, an application, a service, and/or a computing system.

Herein, the term “financial transaction” includes, but is not limitedto, any interaction between two or more parties involving the transfer,or re-categorization, of funds between the parties. Herein, the term“financial transaction data” includes, but is not limited to, electronicdata representing at least one financial transaction and that is capableof being processed by a processor, and/or stored in a memory, and/or isotherwise machine readable.

Herein, the term “product and/or service provider” includes any partyand/or entity that is associated with a user through a financialtransaction represented by financial transaction data.

As used herein, the term “bill” includes, but is not limited to, anaccount statement or other potentially recurring cost and financialtransaction. Currently, bill payments due are represented in personalfinancial management and bill payment system payment due data. Examplesof bills include, but are not limited to: rent payments, utilitypayments, credit card payments, grocery store payments, vehicle costs,etc. Bills are typically associated with larger, well known, and/ornationally or regionally known, payee businesses.

In contrast to the term “bill”, herein the term “invoice” includes, butis not limited to, documents/data associated with a specific productand/or service provided by a business and for which full payment istypically requested via a discrete invoice statement. Herein the term“invoice related financial transaction data” includes data representingall, or part of, an “invoice.” A given discrete invoice is thereforetypically a non-recurring expense and/or is associated with specificproducts and/or services rendered, even though multiple, and evenrecurring identical, invoices can be generated by the same payeebusiness for the same payor customer if multiple products and/orservices, and/or the same products and/or services, are provided.Invoices are typically associated with smaller, regional or local, payeebusinesses than those associated with bills.

Herein the terms “payment,” and/or “payment due,” and/or “payment dueitems” are used interchangeably and include any payment owed by a firstparty, i.e., payor party, to a second party, i.e., a payee party.Consequently, as used herein, the terms “payment” and/or “payment due”include both “bills” and “invoices.”

As used herein, the term “payor user” includes any user of a personalfinancial management and bill payment system associated with an invoiceincluded in invoice related financial transaction data and to whom theinvoice related financial transaction data is directed by a payeebusiness.

As used herein, the term “payee business” includes any party or entityassociated with an invoice included in invoice related financialtransaction data and to whom the invoice amount associated with ininvoice represented in invoice related financial transaction data isowed by a payor user.

DETAILED DISCLOSURE

Embodiments will now be discussed with reference to the accompanyingFIG.s, which depict one or more exemplary embodiments. Embodiments maybe implemented in many different forms and should not be construed aslimited to the embodiments set forth herein, shown in the FIG.s, and/ordescribed below. Rather, these exemplary embodiments are provided toallow a complete disclosure that conveys the principles of theinvention, as set forth in the claims, to those of skill in the art.

In accordance with one embodiment of a method and system for integratingdiscrete invoices into a personal financial management and bill paymentsystem and then aggregating discrete invoices having the same payeebusiness into a single funds transfer transaction, access to invoicerelated financial transaction data generated by the one or more payeebusinesses is obtained.

In one embodiment, the obtained invoice related financial transactiondata represents two or more discrete invoices submitted by one or morepayee businesses requesting payment by one or more payor users of thepersonal financial management and bill payment system.

In one embodiment, the invoice related financial transaction dataincludes payee business identity data associated with each discreteinvoice represented in the invoice related financial transaction data.In one embodiment, the payee business identity data represents theidentity of the payee business associated with each discrete invoicerepresented in the invoice related financial transaction data.

In one embodiment, the invoice related financial transaction data alsoincludes payor user identity data associated with each discrete invoicerepresented in the invoice related financial transaction data. In oneembodiment, the payor user identity data represents the identity of thepayor user associated with each discrete invoice represented in theinvoice related financial transaction data.

In one embodiment, the invoice related financial transaction datafurther includes invoice amount data associated with each discreteinvoice represented in the invoice related financial transaction data.In one embodiment, the invoice amount data represents the payment amountassociated with each discrete invoice represented in the invoice relatedfinancial transaction data.

In accordance with one embodiment, the invoice related financialtransaction data generated by the one or more payee businesses isobtained from a business invoicing system provided to business users ofthe business invoicing system.

As noted above, herein, the term “business invoicing system” includes,but is not limited to, any system through which a business can generate,and/or submit, and/or process invoices requesting payment for productsand/or services provided by the business to customers of the business.Therefore, the term “business invoicing system” includes, but is notlimited to, the following: computing system, desktop system, mobilesystem, and/or wearable device implemented, and/or online, and/orweb-based, storage based, persistence based, business accounting and/orinvoicing systems, services, packages, programs, modules, orapplications; computing system, desktop system, mobile system, and/orwearable device implemented, and/or online, and/or web-based, storagebased, persistence based, business financial transaction aggregationand/or processing systems, services, packages, programs, modules, orapplications; computing system, desktop system, mobile system, and/orwearable device implemented, and/or online, and/or web-based, storagebased, persistence based, business financial management and budgetingsystems, services, packages, programs, modules, or applications;computing system, desktop system, mobile system, and/or wearable deviceimplemented, and/or online, and/or web-based, storage based, persistencebased, business management systems, services, packages, programs,modules, or applications; business electronic tax preparation systems,services, packages, programs, modules, or applications; and variousother business electronic data management systems, services, packages,programs, modules, or applications, whether known at the time offilling, or as developed later.

Specific examples of “business invoicing systems” include, but are notlimited to, the following: QuickBooks™, available from Intuit, Inc. ofMountain View, Calif.; QuickBooks Online™, available from Intuit, Inc.of Mountain View, Calif.; QuickBooks Self-Employed™, available fromIntuit, Inc. of Mountain View, Calif.; TurboTax™ available from Intuit,Inc. of Mountain View, Calif.; TurboTax Online™ available from Intuit,Inc. of Mountain View, Calif.; and/or various other software systemsdiscussed herein, and/or known to those of skill in the art at the timeof filing, and/or as developed after the time of filing.

In some embodiments, the business invoicing system is part of, and/or afeature of, a parent small business financial management system.

In one embodiment, a personal financial management and bill paymentsystem is provided using one or more computing systems.

As noted above, herein, the term “personal financial management and billpayment system” includes, but is not limited to, the following:computing system, desktop system, mobile system, and/or wearable deviceimplemented, and/or online, and/or web-based, storage based, persistencebased, personal financial transaction aggregation and/or processingsystems, services, packages, programs, modules, or applications;computing system, desktop system, mobile system, and/or wearable deviceimplemented, and/or online, and/or web-based, storage based, persistencebased, personal financial management and budgeting systems, services,packages, programs, modules, or applications; computing system, desktopsystem, mobile system, and/or wearable device implemented, and/oronline, and/or web-based, storage based, persistence based, personaldata management systems, services, packages, programs, modules, orapplications; computing system, desktop system, mobile system, and/orwearable device implemented, and/or online, and/or web-based, storagebased, persistence based, personal accounting systems, services,packages, programs, modules, or applications; personal electronic taxpreparation systems, services, packages, programs, modules, orapplications; and various other personal electronic data managementsystems, services, packages, programs, modules, or applications, whetherknown at the time of filling, or as developed later.

As noted above, specific examples of personal financial management andbill payment systems include, but are not limited to the following:Mint™, available from Intuit, Inc. of Mountain View, Calif.; MintOnline™, available from Intuit, Inc. of Mountain View, Calif.; TurboTax™available from Intuit, Inc. of Mountain View, Calif.; TurboTax Online™available from Intuit, Inc. of Mountain View, Calif.; and/or variousother software systems discussed herein, and/or known to those of skillin the art at the time of filing, and/or as developed after the time offiling.

Currently, personal financial management and bill payment systems andbusiness invoicing systems are typically distinct software systemsoperated and/or used by two distinct parties, e.g., a customer of abusiness and an owner of a business, respectively. Therefore, currently,personal financial management and bill payment systems and businessinvoicing systems typically operate in isolation from each other, evenwhen they are offered by the same personal financial management and billpayment system and business invoicing system provider.

As a specific illustrative example, in one embodiment, the personalfinancial management and bill payment system used by a customer of abusiness, or other user, could be a personal financial transactionmanagement system such as Mint™, available from Intuit, Inc. of MountainView, Calif. In this specific illustrative example, a business invoicingsystem, used by a business user, could be a business invoicing systemsuch as QuickBooks™, available from Intuit, Inc. of Mountain View,Calif. As seen in this specific illustrative example, both the personalfinancial management and bill payment system and the business invoicingsystem are offered by the same software system provider, i.e., in thisspecific case, Intuit, Inc. of Mountain View, Calif. Consequently,according to one embodiment, in this specific illustrative example, thepersonal financial management and bill payment system and the businessinvoicing system are provided the opportunity to cross pollinate andcross confirm supported data. This approach has several uniqueadvantages.

In accordance with one embodiment, one or more processors associatedwith one or more computing systems are utilized to obtain access to thebusiness invoicing system and obtain invoice related financialtransaction data generated by the one or more payee businesses.

In accordance with one embodiment, obtaining access to invoice relatedfinancial transaction data generated by the one or more payee businessesincludes, but is not limited to:

-   -   a. obtaining access to personal financial management and bill        payment system user financial transaction data associated with        the personal financial management and bill payment system, the        personal financial management and bill payment system user        financial transaction data representing financial transactions        associated with users of the personal financial management and        bill payment system;    -   b. analyzing the personal financial management and bill payment        system user financial transaction data associated with a first        payor user to identify payee data included in the financial        transaction data associated with the first payor user, the payee        data representing one or more payees associated with first payor        user financial transactions associated with the first payor user        represented by a portion of the personal financial management        and bill payment system user financial transaction data        associated with the first payor user;    -   c. obtaining access to business invoicing system business user        identification data associated with a business invoicing system,        the business user identification data representing business        users of the business invoicing system;    -   d. accessing the payee data and the business user identification        data and analyzing the payee data and business user        identification data to determine if a payee represented in the        payee data matches a business user of the business invoicing        system represented in the business user identification data;    -   e. identifying a payee represented in the payee data that        matches a business user of the business invoicing system        represented in the business user identification data, the payee        being a payee associated with first financial transaction data        representing a first financial transaction included in the        personal financial management and bill payment system user        financial transaction data associated with the first payor user;    -   f. designating the payee represented in the payee data that        matches the business user of the business invoicing system as a        first payee business;    -   g. transforming status data associated with the first financial        transaction data representing the first financial transaction to        first invoice related financial transaction data;    -   h. processing the first invoice related financial transaction        data as invoice related financial transaction data; and    -   i. providing the first payee business the capability to provide        invoicing data representing invoices generated by the first        payee business to the first payor user of the personal financial        management and bill payment system through the personal        financial management and bill payment system.

In accordance with one embodiment, obtaining access to invoice relatedfinancial transaction data generated by the one or more payee businessesincludes, but is not limited to:

-   -   a. obtaining access to personal financial management and bill        payment system user identification data associated with users of        a personal financial management and bill payment system;    -   b. obtaining access to invoicing data generated through a        business invoicing system, the invoicing data representing        invoices sent from payee business users of the business        invoicing system to payor customers of the payee business users        of the business invoicing system;    -   c. monitoring the invoicing data and identifying first invoice        data representing an invoice generated by a first payee business        user of the business invoicing system associated with a first        payor customer of the first payee business user of the business        invoicing system;    -   d. analyzing the first invoice data to identify first payor        customer identification data associated with the first payor        customer of the first payee business user of the business        invoicing system;    -   e. analyzing the personal financial management and bill payment        system user identification data and the first payor customer        identification data to determine if the first payor customer        associated with the first payor customer identification data is        a first payor user of the personal financial management and bill        payment system;    -   f. if a determination is made that the first payor customer        associated with the first payor customer identification data is        a first payor user of the personal financial management and bill        payment system, designating the first payor customer as a first        payor user of the personal financial management and bill payment        system; and    -   g. providing the first payee business user of the business        invoicing system the capability to provide invoicing data        representing invoices generated by the first payee business user        of the business invoicing system to the first payor user of the        personal financial management and bill payment system through        the personal financial management and bill payment system.

In accordance with one embodiment, obtaining access to invoice relatedfinancial transaction data generated by the one or more payee businessesincludes, but is not limited to:

-   -   a. obtaining access to personal financial management and bill        payment system user identification data associated with users of        a personal financial management and bill payment system;    -   b. obtaining access to business invoicing system payor customer        identification data generated through a business invoicing        system, the business invoicing system payor customer        identification data being associated with payor customers of        user payee businesses of a business invoicing system;    -   c. analyzing the personal financial management and bill payment        system user identification data and the business invoicing        system payor customer identification data to identify payor        users of the personal financial management and bill payment        system that are payor customers of business users of the        business invoicing system;    -   d. identifying a payor user of the personal financial management        and bill payment system that is a payor customer of a payee        business user of the business invoicing system;    -   e. designating the payor user of the personal financial        management and bill payment system a first payor user of the        personal financial management and bill payment system;    -   f. providing the first payor user of the personal financial        management and bill payment system the opportunity to integrate        invoices generated by the first payee business user of the        business invoicing system into the personal financial management        and bill payment system; and    -   g. if the first payor user of the personal financial management        and bill payment system agrees to integrate invoices generated        by the first payee business user of the business invoicing        system into the personal financial management and bill payment        system, providing the first payee business user of the business        invoicing system the capability to provide invoice data        representing invoices generated by the first payee business user        of the business invoicing system to the first payor user of the        personal financial management and bill payment system through        the personal financial management and bill payment system.

In accordance with one embodiment, obtaining access to invoice relatedfinancial transaction data generated by the one or more payee businessesincludes any method, system, process and/or procedure for obtainingaccess to invoice related financial transaction data generated by theone or more payee businesses as discussed herein, known in the art atthe time of filing, and/or as developed/made available after the time offiling.

In accordance with one embodiment, obtaining access to invoice relatedfinancial transaction data generated by the one or more payee businessesincludes any method, system, process and/or procedure for obtainingaccess to invoice related financial transaction data generated by theone or more payee businesses as discussed in: U.S. patent applicationSer. No. 15/140,117 (docket number INTU169676), filed on behalf of thesame Inventors of the present patent application, filed on Apr. 27,2016, entitled “METHOD AND SYSTEM FOR PROVIDING INVOICES GENERATEDTHROUGH A BUSINESS INVOICING SYSTEM TO A CUSTOMER USER OF A PERSONALFINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM,” which is hereinincorporated by reference in its entirety as if it were fully set forthherein; and/or U.S. patent application Ser. No. 15/140,131 (docketnumber INTU169677), filed on behalf of the same Inventors of the presentpatent application, filed on Apr. 27, 2016, entitled “METHOD AND SYSTEMFOR IDENTIFYING INVOICES THAT ARE PAID THROUGH A PERSONAL FINANCIALMANAGEMENT AND BILL PAYMENT SYSTEM,” which is herein incorporated byreference in its entirety as if it were fully set forth herein; and/orU.S. patent application Ser. No. 15/142,708 (docket number INTU169678),filed on behalf of the same Inventors of the present patent application,filed on Apr. 29, 2016, entitled “METHOD AND SYSTEM FOR INTEGRATINGBUSINESS INVOICES INTO A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENTSYSTEM,” which is herein incorporated by reference in its entirety as ifit were fully set forth herein.

In accordance with one embodiment, the invoice related financialtransaction data is integrated into personal financial management andbill payment system payment due data associated with a personalfinancial management and bill payment system.

In one embodiment, the personal financial management and bill paymentsystem payment due data represents one or more payments due associatedwith one or more users of the personal financial management and billpayment system as payment due items to be paid through the personalfinancial management and bill payment system.

In accordance with one embodiment, the invoice related financialtransaction data is integrated into personal financial management andbill payment system payment due data associated with a personalfinancial management and bill payment system by assigning a personalfinancial management and bill payment system financial transactioncategory to the discrete invoices represented in the invoice relatedfinancial transaction data.

In accordance with one embodiment, the invoice related financialtransaction data is integrated into personal financial management andbill payment system payment due data associated with a personalfinancial management and bill payment system by providing the discreteinvoices represented in the invoice related financial transaction dataas line items in a payment due item listing generated through thepersonal financial management and bill payment system.

In accordance with one embodiment, the invoice related financialtransaction data is integrated into personal financial management andbill payment system payment due data associated with a personalfinancial management and bill payment system by assigning a personalfinancial management and bill payment system financial transactioncategory to the discrete invoices represented in the invoice relatedfinancial transaction data.

In accordance with one embodiment, the invoice related financialtransaction data is integrated into personal financial management andbill payment system payment due data associated with a personalfinancial management and bill payment system by any method, system,process and/or procedure for integrating invoice related financialtransaction data into personal financial management and bill paymentsystem payment due data as discussed herein, known in the art at thetime of filing, and/or as developed/made available after the time offiling.

In accordance with various embodiments, the invoice related financialtransaction data is integrated into personal financial management andbill payment system payment due data associated with a personalfinancial management and bill payment system by any method, system,process and/or procedure for integrating invoice related financialtransaction data into personal financial management and bill paymentsystem payment due data as discussed in: U.S. patent application Ser.No. 15/140,117 (docket number INTU169676), filed on behalf of the sameInventors of the present patent application, filed on Apr. 27, 2016,entitled “METHOD AND SYSTEM FOR PROVIDING INVOICES GENERATED THROUGH ABUSINESS INVOICING SYSTEM TO A CUSTOMER USER OF A PERSONAL FINANCIALMANAGEMENT AND BILL PAYMENT SYSTEM,” which is herein incorporated byreference in its entirety as if it were fully set forth herein; and/orU.S. patent application Ser. No. 15/140,131 (docket number INTU169677),filed on behalf of the same Inventors of the present patent application,filed on Apr. 27, 2016, entitled “METHOD AND SYSTEM FOR IDENTIFYINGINVOICES THAT ARE PAID THROUGH A PERSONAL FINANCIAL MANAGEMENT AND BILLPAYMENT SYSTEM,” which is herein incorporated by reference in itsentirety as if it were fully set forth herein; and/or U.S. patentapplication Ser. No. 15/142,708 (docket number INTU169678), filed onbehalf of the same Inventors of the present patent application, filed onApr. 29, 2016, entitled “METHOD AND SYSTEM FOR INTEGRATING BUSINESSINVOICES INTO A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM,”which is herein incorporated by reference in its entirety as if it werefully set forth herein.

In accordance with one embodiment, invoice payment request data isreceived from one or more users of the personal financial management andbill payment system.

As noted above, personal financial management and bill payment systemshelp a personal financial management and bill payment system user, orany authorized party acting on behalf of a personal financial managementand bill payment system user, obtain financial transaction datarepresenting financial transactions conducted by the user,process/analyze the financial transaction data, display categorizedfinancial transaction data, generate financial transaction reports,generate bills due and payment due reports, and/or make manual,semi-automated, and/or automatic bill payments through the personalfinancial management and bill payment system.

As also noted above, some personal financial management and bill paymentsystems help users manage their finances and/or track theirexpenditures/financial transactions by providing a centralized interfacewith banks, credit card companies, and various other financialinstitutions, for electronically identifying and categorizing the user'sfinancial transaction data. Currently, personal financial management andbill payment systems typically obtain electronic financial transactiondata, such as payee data, payment amount data, transaction date data,etc. via communication with banks, credit card providers, or otherfinancial institutions, using electronic data transfer systems, orvarious other systems for obtaining/transferring financial transactiondata.

In addition, some personal financial management and bill payment systemsinclude a payment due report/display generation feature. Typically, apayment due report includes personal financial management and billpayment system payment due data representing a listing of payments due,e.g., bill payment due items, within a defined period of time, such as amonth, which require the user's attention.

As also noted above, in some cases, the users of the personal financialmanagement and bill payment systems are also provided a bill paymentservice and the capability to make payments on a manual, semi-automatic,i.e., with user approval, or automatic, basis to various payees. Inorder to make these payments, the users of the personal financialmanagement and bill payment systems typically enter data into thepersonal financial management and bill payment systems directing, orrequesting, that one or more payments be made to one or more payees on aone-time, recurring, automatic, semi-automatic, or manual basis.

In the present embodiments, where invoice related financial transactiondata has been integrated into the personal financial management and billpayment system payment due data, invoice payment requests are made bythe users of the personal financial management and bill payment systemsby entering, and/or providing, invoice payment request data.

In one embodiment, the invoice payment request data received by thepersonal financial management and bill payment system represents one ormore requests from one or more users of the personal financialmanagement and bill payment system to pay one or more requested invoicepayment amounts associated with one or more discrete invoice paymentrequest related invoices represented in the invoice related financialtransaction data through the personal financial management and billpayment system.

In accordance with one embodiment, access to the personal financialmanagement and bill payment system and the personal financial managementand bill payment system payment due data, including the integratedinvoice related financial transaction data, and the invoice paymentrequest data is obtained.

In accordance with one embodiment, one or more processors associatedwith one or more computing systems are utilized to obtain access to thepersonal financial management and bill payment system and the personalfinancial management and bill payment system payment due data, includingthe integrated invoice related financial transaction data, and theinvoice payment request data.

In accordance with one embodiment, the invoice payment request data isanalyzed by one or more processors associated with one or more computingsystems to identify discrete invoice payment request related invoicedata representing one or more discrete invoice payment request relatedinvoices represented in the invoice related financial transaction data.

In accordance with one embodiment, the integrated invoice relatedfinancial transaction data associated with the discrete invoice paymentrequest related invoices is analyzed by one or more processorsassociated with one or more computing systems to identify the payeebusiness identity data associated with each discrete invoice paymentrequest related invoice represented in the discrete invoice paymentrequest related invoice data.

In accordance with one embodiment, a first payee business represented inthe payee business identity data associated with two or more discretefirst payee business invoice payment request related invoicesrepresented in the discrete invoice payment request related invoice datais identified by one or more processors associated with one or morecomputing systems.

In accordance with one embodiment, all the invoice related financialtransaction data associated with the two or more discrete invoicepayment request related invoices is aggregated by one or more processorsassociated with one or more computing systems to generate aggregatedfirst payee business invoice payment request invoice data.

In accordance with one embodiment, the aggregated first payee businessinvoice payment request invoice data is analyzed by one or moreprocessors associated with one or more computing systems to identify therequested invoice payment amount data associated with each of the two ormore discrete invoice payment request related invoices.

In accordance with one embodiment, the requested invoice payment amountdata associated with each of the two or more discrete invoice paymentrequest related invoices is processed and summed by one or moreprocessors associated with one or more computing systems to generateaggregated total first payee business invoice payment amount datarepresenting a total requested invoice payment amount for the firstpayee business requested by two or more users of the personal financialmanagement and bill payment system.

In accordance with one embodiment, the aggregated total first payeebusiness invoice payment amount data is then processed by one or moreprocessors associated with one or more computing systems as a singlefirst payee business funds transfer item using the personal financialmanagement and bill payment system.

In accordance with one embodiment, processing the aggregated total firstpayee business invoice payment amount data as a single first payeebusiness funds transfer item using the personal financial management andbill payment system includes providing the aggregated total first payeebusiness invoice payment amount data as a line item in a funds transferitem listing generated through the personal financial management andbill payment system.

In accordance with one embodiment, processing the aggregated total firstpayee business invoice payment amount data as a single first payeebusiness funds transfer item using the personal financial management andbill payment system includes applying one or more aggregated first payeebusiness invoice payment request invoice data processing rules to theaggregated first payee business invoice payment request invoice data.

In accordance with one embodiment, the aggregated first payee businessinvoice payment request invoice data processing rules include, but arenot limited to, an aggregated first payee business invoice paymentrequest invoice data processing rule limiting the aggregated total firstpayee business invoice payment amount to a threshold amount.

Using this aggregated first payee business invoice payment requestinvoice data processing rule, the financial risk associated with thesingle first payee business funds transfer transaction is limited to thethreshold amount.

In accordance with one embodiment, the aggregated first payee businessinvoice payment request invoice data processing rules include, but arenot limited to, an aggregated first payee business invoice paymentrequest invoice data processing rule limiting the total number ofdiscrete invoices represented in the aggregated first payee businessinvoice payment request invoice data to a threshold number of discreteinvoices.

Using this aggregated first payee business invoice payment requestinvoice data processing rule, the total liability associated with thesingle first payee business funds transfer transaction is limited to atotal aggregated invoice amount associated with a threshold number ofdiscrete invoices, thereby limiting the financial risk.

In accordance with one embodiment, the aggregated first payee businessinvoice payment request invoice data processing rules include any of theaggregated first payee business invoice payment request invoice dataprocessing rules desired, and/or as discussed herein, known in the artat the time of filing, and/or as developed/made available after the timeof filing.

FIG. 1 is a high level functionality-based block diagram of a hardwareand production environment 100 for integrating discrete invoices into apersonal financial management and bill payment system and thenaggregating discrete invoices having the same payee business into asingle funds transfer transaction, in accordance with one embodiment.

As seen in FIG. 1, in this specific illustrative example, productionenvironment 100 includes: personal financial management and bill paymentsystem computing system environment 110, including personal financialmanagement and bill payment system 111; business invoicing systemcomputing system environment 120, including business invoicing system121; and process computing system environment 130, including processcomputing system 131.

As seen in FIG. 1, in the specific illustrative example of FIG. 1,personal financial management and bill payment system 111 includespersonal financial management and bill payment system payment due data113 associated with one or more users of personal financial managementand bill payment system 111 and invoice payment request data 114representing one or more requests from one or more users (not shown) ofpersonal financial management and bill payment system 111 to pay one ormore requested invoice payment amounts associated with one or morediscrete invoice payment request related invoices represented in invoicerelated financial transaction data 123 through personal financialmanagement and bill payment system 111

In one embodiment, personal financial management and bill payment systempayment due data 113 represents one or more bills associated with one ormore users (not shown) of personal financial management and bill paymentsystem 111 to be paid through personal financial management and billpayment system 111. In one embodiment, personal financial management andbill payment system payment due data 113 includes data representing apayment due item listing (not shown).

As noted, in one embodiment, invoice payment request data 114 representsone or more requests from one or more users (not shown) of personalfinancial management and bill payment system 111 to pay one or morerequested invoice payment amounts associated with one or more discreteinvoice payment request related invoices represented in invoice relatedfinancial transaction data 123 through personal financial management andbill payment system 111.

As seen in FIG. 1, in the specific illustrative example of FIG. 1,business invoicing system 121 includes invoice related financialtransaction data 123 generated by the one or more payee businesses (notshown). In one embodiment, invoice related financial transaction data123 represents two or more discrete invoices (not shown) submitted byone or more payee businesses (not shown) requesting payment by one ormore payor users (not shown) of personal financial management and billpayment system 111.

In one embodiment, invoice related financial transaction data 123includes payee business identity data associated with each discreteinvoice represented in the invoice related financial transaction data(not shown). In one embodiment, the payee business identity datarepresents the identity of the payee business associated with eachdiscrete invoice represented in the invoice related financialtransaction data.

In one embodiment, invoice related financial transaction data 123 alsoincludes payor user identity data associated with each discrete invoicerepresented in the invoice related financial transaction data (notshown). In one embodiment, the payor user identity data represents theidentity of the payor user associated with each discrete invoicerepresented in the invoice related financial transaction data.

In one embodiment, invoice related financial transaction data 123further includes invoice amount data associated with each discreteinvoice represented in the invoice related financial transaction data(not shown). In one embodiment, the invoice amount data represents thepayment amount associated with each discrete invoice represented in theinvoice related financial transaction data.

As seen in FIG. 1, in the specific illustrative example of FIG. 1,process computing system 131 includes personal financial management andbill payment system access module 133 for obtaining access to personalfinancial management and bill payment system 111, personal financialmanagement and bill payment system payment due data 113 and invoicepayment request data 114.

As seen in FIG. 1, in the specific illustrative example of FIG. 1,process computing system 131 includes business invoicing system accessmodule 134, i.e., one example of an invoice related financialtransaction data acquisition module, for obtaining access to invoicerelated financial transaction data 123.

As seen in FIG. 1, in the specific illustrative example of FIG. 1,process computing system 131 includes integration module 135 forintegrating invoice related financial transaction data 123 data intopersonal financial management and bill payment system payment due data113 associated with personal financial management and bill paymentsystem 111.

As seen in FIG. 1, in the specific illustrative example of FIG. 1,process computing system 131 includes discrete invoice payment requestrelated invoice data identification module 137 for analyzing invoicepayment request data 123 to identify discrete invoice payment requestrelated invoice data 143 representing one or more discrete invoicepayment request related invoices (not shown) represented in integratedinvoice related financial transaction data 123.

As seen in FIG. 1, in the specific illustrative example of FIG. 1,process computing system 131 includes payee business identity dataidentification module 139 for analyzing discrete invoice payment requestrelated invoice data 143 to identify payee business identity data 140associated with each discrete invoice payment request related invoice(not shown) represented in discrete invoice payment request relatedinvoice data 143 and identifying a first payee business (not shown)represented in payee business identity data 140 associated with two ormore discrete first payee business invoice payment request relatedinvoices (not shown) represented in discrete invoice payment requestrelated invoice data 143.

As seen in FIG. 1, in the specific illustrative example of FIG. 1,process computing system 131 includes aggregation module 151 foraggregating all the first payor user invoice related financialtransaction data representing the two or more discrete invoices ofdiscrete invoice payment request related invoice data 143 that includepayee business identity data 140 identifying the first payee business togenerate the aggregated first payee business invoice payment requestinvoice data 153.

As seen in FIG. 1, in the specific illustrative example of FIG. 1,process computing system 131 includes invoice amount data identificationmodule 155 for analyzing aggregated first payee business invoice paymentrequest invoice data 153 to identify requested invoice payment amountdata (not shown) associated with each of the two or more discreteinvoice payment request related invoices (not shown) of discrete invoicepayment request related invoice data 143.

As seen in FIG. 1, in the specific illustrative example of FIG. 1,process computing system 131 includes aggregated total first payeebusiness invoice payment amount data calculation module 157 for addingthe requested invoice payment amount data associated with each of thetwo or more discrete invoice payment request related invoices (notshown) of discrete invoice payment request related invoice data 143 frominvoice amount data identification module 155 to generate aggregatedtotal first payee business invoice payment amount data 159 representinga total requested invoice payment amount for the first payee businessrequested by two or more users of personal financial management and billpayment system 111.

As seen in FIG. 1, in the specific illustrative example of FIG. 1,process computing system 131 includes aggregated total first payeebusiness invoice payment amount data processing module 161 forprocessing aggregated total first payee business invoice payment amountdata 159 as a single first payee business funds transfer item usingpersonal financial management and bill payment system 111.

The disclosed embodiments provide an efficient, effective, and highlyadaptable solution to the long standing technical problem in the billpayment, invoice processing, and financial management arts ofautomatically integrating invoice related financial transaction datainto a personal financial management and bill payment system, and/oridentifying, or distinguishing, invoice related financial transactiondata, and then aggregating requested invoice payment amounts associatedwith invoices represented in the invoice related financial transactiondata having the same payee business into a single funds transfertransaction item to be processed by the personal financial managementand bill payment system.

However, the disclosed method and system for integrating discreteinvoices into a personal financial management and bill payment systemand then aggregating discrete invoices having the same payee businessinto a single funds transfer transaction does not encompass, embody, orpreclude other forms of innovation in the area of automated financialtransaction bill payment processing and invoicing. In addition, thedisclosed method and system for integrating discrete invoices into apersonal financial management and bill payment system and thenaggregating discrete invoices having the same payee business into asingle funds transfer transaction is not related to any fundamentaleconomic practice, fundamental data processing practice, mental steps,or pen and paper based solution. In fact, the disclosed embodiments aredirected to providing solutions to the relatively new problemsassociated with the automatic processing and display of electronicfinancial transaction data obtained from multiple sources, makingelectronic bill payments, and the management and processing of largeamounts of data, i.e., “big data.” Consequently, the disclosed methodand system for integrating discrete invoices into a personal financialmanagement and bill payment system and then aggregating discreteinvoices having the same payee business into a single funds transfertransaction is not directed to, does not encompass, and is not merely,an abstract idea or concept.

In addition, the disclosed method and system for integrating discreteinvoices into a personal financial management and bill payment systemand then aggregating discrete invoices having the same payee businessinto a single funds transfer transaction provides for significantimprovements to the technical fields of electronic transaction dataprocessing, invoicing, financial transaction categorization, informationdissemination, data processing, data management, data filtering andmining, automatic electronic bill payment, and user experience.

In addition, by allowing for the integration of invoices and invoicedata into a personal financial management and bill payment system, thedisclosed method and system for integrating discrete invoices into apersonal financial management and bill payment system and thenaggregating discrete invoices having the same payee business into asingle funds transfer transaction helps users of the personal financialmanagement and bill payment system identify and pay their invoices.This, in turn, helps avoid the reissuance and repeated transmission ofpayment due reminders and for the entry, processing, and dissemination,of redundant invoice data; thereby eliminating unnecessary data analysisbefore resources are allocated to processing, and/or correcting,redundant reminder data and the redundant reminder data is furthertransmitted/distributed.

Consequently, using the disclosed method and system for integratingdiscrete invoices into a personal financial management and bill paymentsystem and then aggregating discrete invoices having the same payeebusiness into a single funds transfer transaction results in moreefficient use of human and non-human resources, fewer processor cyclesbeing utilized, reduced memory utilization, and less communicationsbandwidth being utilized to relay data to, and from, backend systems andclient systems.

As a result, computing systems are transformed into faster, moreefficient, and more effective computing systems by implementing themethod and system for integrating discrete invoices into a personalfinancial management and bill payment system and then aggregatingdiscrete invoices having the same payee business into a single fundstransfer transaction.

In addition, the disclosed method and system for integrating discreteinvoices into a personal financial management and bill payment systemand then aggregating discrete invoices having the same payee businessinto a single funds transfer transaction provides for the entry,processing, and dissemination, of only relevant portions of data;thereby eliminating unnecessary data analysis and correction beforeresources are allocated to processing, and/or correcting,faulty/irrelevant data, and/or the faulty/irrelevant data is furthertransmitted/distributed.

In addition, by aggregating requested invoice payment amounts associatedwith multiple invoices represented in the invoice related financialtransaction data having the same payee business into single fundstransfer item, the disclosed method and system for integrating discreteinvoices into a personal financial management and bill payment systemand then aggregating discrete invoices having the same payee businessinto a single funds transfer transaction provides for the processing anddissemination of invoice related financial transaction data representingmultiple discrete invoices as a single funds transfer entity/object.This, in turn, helps avoid the processing and transmission of multipleindividual invoice payment related data sets and related funds transfertransaction data sets.

Consequently, using the disclosed method and system for integratingdiscrete invoices into a personal financial management and bill paymentsystem and then aggregating discrete invoices having the same payeebusiness into a single funds transfer transaction results in moreefficient use of human and non-human resources, fewer processor cyclesbeing utilized, reduced memory utilization, and less communicationsbandwidth being utilized to relay data to, and from, backend systems andclient systems.

As a result, computing systems are transformed into faster, moreefficient, and more effective computing systems by implementing themethod and system for integrating discrete invoices into a personalfinancial management and bill payment system and then aggregatingdiscrete invoices having the same payee business into a single fundstransfer transaction.

Process

In accordance with one embodiment, invoice related financial transactiondata is obtained and integrated into a personal financial management andbill payment system. Then, all requested invoice payments associatedwith invoices represented in the invoice related financial transactiondata having the same payee business are identified and aggregated.

In one embodiment, the amounts of the aggregated requested invoicepayments for the payee business are then summed to determine the totalamount to be transferred to the payee business and this total amount tobe transferred to the payee business is then processed as a single fundstransfer item by the personal financial management and bill paymentsystem.

Consequently, using the disclosed embodiments, invoices represented ininvoice related financial transaction data can be integrated into, andprocessed by, the personal financial management and bill payment systemat minimal cost to the parties involved, using minimal resources, and ina seamless and effective manner.

Therefore, the disclosed embodiments provide an efficient, effective,and highly adaptable solution to the long standing technical problem inthe bill payment, invoice processing, and financial management arts ofautomatically integrating invoice related financial transaction datainto a personal financial management and bill payment system, and/oridentifying, or distinguishing, invoice related financial transactiondata, and then aggregating requested invoice payment amounts associatedwith invoices represented in the invoice related financial transactiondata having the same payee business into a single funds transfertransaction item to be processed by the personal financial managementand bill payment system.

Consequently, using the disclosed embodiments, invoices represented ininvoice related financial transaction data can be integrated into, andprocessed by, the personal financial management and bill payment systemat minimal cost to the parties involved, using minimal resources, and ina seamless and effective manner.

Therefore, the disclosed embodiments provide an efficient, effective,and highly adaptable solution to the long standing technical problem inthe bill payment, invoice processing, and financial management arts ofautomatically integrating invoice related financial transaction datainto a personal financial management and bill payment system, and/oridentifying, or distinguishing, invoice related financial transactiondata, and then aggregating requested invoice payment amounts associatedwith invoices represented in the invoice related financial transactiondata having the same payee business into a single funds transfertransaction item to be processed by the personal financial managementand bill payment system.

FIG. 2 is a flow chart representing one example of a process 200 forintegrating discrete invoices into a personal financial management andbill payment system and then aggregating discrete invoices having thesame payee business into a single funds transfer transaction inaccordance with one embodiment.

As seen in FIG. 2, process 200 for integrating discrete invoices into apersonal financial management and bill payment system and thenaggregating discrete invoices having the same payee business into asingle funds transfer transaction begins at ENTER OPERATION 201 andprocess flow proceeds to OBTAIN ACCESS TO INVOICE RELATED FINANCIALTRANSACTION DATA REPRESENTING TWO OR MORE DISCRETE INVOICES SUBMITTED BYONE OR MORE PAYEE BUSINESSES REQUESTING PAYMENT BY PAYOR USERS OF THEPERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 203.

In one embodiment, at OBTAIN ACCESS TO INVOICE RELATED FINANCIALTRANSACTION DATA REPRESENTING TWO OR MORE DISCRETE INVOICES SUBMITTED BYONE OR MORE PAYEE BUSINESSES REQUESTING PAYMENT BY PAYOR USERS OF THEPERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 203,access to invoice related financial transaction data generated by theone or more payee businesses is obtained.

In one embodiment, the obtained invoice related financial transactiondata of OBTAIN ACCESS TO INVOICE RELATED FINANCIAL TRANSACTION DATAREPRESENTING TWO OR MORE DISCRETE INVOICES SUBMITTED BY ONE OR MOREPAYEE BUSINESSES REQUESTING PAYMENT BY PAYOR USERS OF THE PERSONALFINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 203 representstwo or more discrete invoices submitted by one or more payee businessesrequesting payment by one or more payor users of the personal financialmanagement and bill payment system.

In one embodiment, the invoice related financial transaction data ofOBTAIN ACCESS TO INVOICE RELATED FINANCIAL TRANSACTION DATA REPRESENTINGTWO OR MORE DISCRETE INVOICES SUBMITTED BY ONE OR MORE PAYEE BUSINESSESREQUESTING PAYMENT BY PAYOR USERS OF THE PERSONAL FINANCIAL MANAGEMENTAND BILL PAYMENT SYSTEM OPERATION 203 includes payee business identitydata associated with each discrete invoice represented in the invoicerelated financial transaction data. In one embodiment, the payeebusiness identity data represents the identity of the payee businessassociated with each discrete invoice represented in the invoice relatedfinancial transaction data.

In one embodiment, the invoice related financial transaction data ofOBTAIN ACCESS TO INVOICE RELATED FINANCIAL TRANSACTION DATA REPRESENTINGTWO OR MORE DISCRETE INVOICES SUBMITTED BY ONE OR MORE PAYEE BUSINESSESREQUESTING PAYMENT BY PAYOR USERS OF THE PERSONAL FINANCIAL MANAGEMENTAND BILL PAYMENT SYSTEM OPERATION 203 also includes payor user identitydata associated with each discrete invoice represented in the invoicerelated financial transaction data. In one embodiment, the payor useridentity data represents the identity of the payor user associated witheach discrete invoice represented in the invoice related financialtransaction data.

In one embodiment, the invoice related financial transaction data ofOBTAIN ACCESS TO INVOICE RELATED FINANCIAL TRANSACTION DATA REPRESENTINGTWO OR MORE DISCRETE INVOICES SUBMITTED BY ONE OR MORE PAYEE BUSINESSESREQUESTING PAYMENT BY PAYOR USERS OF THE PERSONAL FINANCIAL MANAGEMENTAND BILL PAYMENT SYSTEM OPERATION 203 further includes invoice amountdata associated with each discrete invoice represented in the invoicerelated financial transaction data. In one embodiment, the invoiceamount data represents the payment amount associated with each discreteinvoice represented in the invoice related financial transaction data.

In accordance with one embodiment, at OBTAIN ACCESS TO INVOICE RELATEDFINANCIAL TRANSACTION DATA REPRESENTING TWO OR MORE DISCRETE INVOICESSUBMITTED BY ONE OR MORE PAYEE BUSINESSES REQUESTING PAYMENT BY PAYORUSERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEMOPERATION 203 the invoice related financial transaction data generatedby the one or more payee businesses is obtained from a businessinvoicing system provided to business users of the business invoicingsystem.

In accordance with one embodiment, at OBTAIN ACCESS TO INVOICE RELATEDFINANCIAL TRANSACTION DATA REPRESENTING TWO OR MORE DISCRETE INVOICESSUBMITTED BY ONE OR MORE PAYEE BUSINESSES REQUESTING PAYMENT BY PAYORUSERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEMOPERATION 203 one or more processors associated with one or morecomputing systems are utilized to obtain access to the businessinvoicing system and obtain invoice related financial transaction datagenerated by the one or more payee businesses.

In accordance with one embodiment, obtaining access to invoice relatedfinancial transaction data generated by the one or more payee businessesat OBTAIN ACCESS TO INVOICE RELATED FINANCIAL TRANSACTION DATAREPRESENTING TWO OR MORE DISCRETE INVOICES SUBMITTED BY ONE OR MOREPAYEE BUSINESSES REQUESTING PAYMENT BY PAYOR USERS OF THE PERSONALFINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 203 includes, butis not limited to:

-   -   a. obtaining access to personal financial management and bill        payment system user financial transaction data associated with        the personal financial management and bill payment system, the        personal financial management and bill payment system user        financial transaction data representing financial transactions        associated with users of the personal financial management and        bill payment system;    -   b. analyzing the personal financial management and bill payment        system user financial transaction data associated with a first        payor user to identify payee data included in the financial        transaction data associated with the first payor user, the payee        data representing one or more payees associated with first payor        user financial transactions associated with the first payor user        represented by a portion of the personal financial management        and bill payment system user financial transaction data        associated with the first payor user;    -   c. obtaining access to business invoicing system business user        identification data associated with a business invoicing system,        the business user identification data representing business        users of the business invoicing system;    -   d. accessing the payee data and the business user identification        data and analyzing the payee data and business user        identification data to determine if a payee represented in the        payee data matches a business user of the business invoicing        system represented in the business user identification data;    -   e. identifying a payee represented in the payee data that        matches a business user of the business invoicing system        represented in the business user identification data, the payee        being a payee associated with first financial transaction data        representing a first financial transaction included in the        personal financial management and bill payment system user        financial transaction data associated with the first payor user;    -   f. designating the payee represented in the payee data that        matches the business user of the business invoicing system as a        first payee business;    -   g. transforming status data associated with the first financial        transaction data representing the first financial transaction to        first invoice related financial transaction data;    -   h. processing the first invoice related financial transaction        data as invoice related financial transaction data; and    -   i. providing the first payee business the capability to provide        invoicing data representing invoices generated by the first        payee business to the first payor user of the personal financial        management and bill payment system through the personal        financial management and bill payment system.

In accordance with one embodiment, obtaining access to invoice relatedfinancial transaction data generated by the one or more payee businessesat OBTAIN ACCESS TO INVOICE RELATED FINANCIAL TRANSACTION DATAREPRESENTING TWO OR MORE DISCRETE INVOICES SUBMITTED BY ONE OR MOREPAYEE BUSINESSES REQUESTING PAYMENT BY PAYOR USERS OF THE PERSONALFINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 203 includes, butis not limited to:

-   -   a. obtaining access to personal financial management and bill        payment system user identification data associated with users of        a personal financial management and bill payment system;    -   b. obtaining access to invoicing data generated through a        business invoicing system, the invoicing data representing        invoices sent from payee business users of the business        invoicing system to payor customers of the payee business users        of the business invoicing system;    -   c. monitoring the invoicing data and identifying first invoice        data representing an invoice generated by a first payee business        user of the business invoicing system associated with a first        payor customer of the first payee business user of the business        invoicing system;    -   d. analyzing the first invoice data to identify first payor        customer identification data associated with the first payor        customer of the first payee business user of the business        invoicing system;    -   e. analyzing the personal financial management and bill payment        system user identification data and the first payor customer        identification data to determine if the first payor customer        associated with the first payor customer identification data is        a first payor user of the personal financial management and bill        payment system;    -   f. if a determination is made that the first payor customer        associated with the first payor customer identification data is        a first payor user of the personal financial management and bill        payment system, designating the first payor customer as a first        payor user of the personal financial management and bill payment        system; and    -   g. providing the first payee business user of the business        invoicing system the capability to provide invoicing data        representing invoices generated by the first payee business user        of the business invoicing system to the first payor user of the        personal financial management and bill payment system through        the personal financial management and bill payment system.

In accordance with one embodiment, obtaining access to invoice relatedfinancial transaction data generated by the one or more payee businessesat OBTAIN ACCESS TO INVOICE RELATED FINANCIAL TRANSACTION DATAREPRESENTING TWO OR MORE DISCRETE INVOICES SUBMITTED BY ONE OR MOREPAYEE BUSINESSES REQUESTING PAYMENT BY PAYOR USERS OF THE PERSONALFINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 203 includes, butis not limited to:

-   -   a. obtaining access to personal financial management and bill        payment system user identification data associated with users of        a personal financial management and bill payment system;    -   b. obtaining access to business invoicing system payor customer        identification data generated through a business invoicing        system, the business invoicing system payor customer        identification data being associated with payor customers of        user payee businesses of a business invoicing system;    -   c. analyzing the personal financial management and bill payment        system user identification data and the business invoicing        system payor customer identification data to identify payor        users of the personal financial management and bill payment        system that are payor customers of business users of the        business invoicing system;    -   d. identifying a payor user of the personal financial management        and bill payment system that is a payor customer of a payee        business user of the business invoicing system;    -   e. designating the payor user of the personal financial        management and bill payment system a first payor user of the        personal financial management and bill payment system;    -   f. providing the first payor user of the personal financial        management and bill payment system the opportunity to integrate        invoices generated by the first payee business user of the        business invoicing system into the personal financial management        and bill payment system; and    -   g. if the first payor user of the personal financial management        and bill payment system agrees to integrate invoices generated        by the first payee business user of the business invoicing        system into the personal financial management and bill payment        system, providing the first payee business user of the business        invoicing system the capability to provide invoice data        representing invoices generated by the first payee business user        of the business invoicing system to the first payor user of the        personal financial management and bill payment system through        the personal financial management and bill payment system.

In accordance with one embodiment, obtaining access to invoice relatedfinancial transaction data generated by the one or more payee businessesat OBTAIN ACCESS TO INVOICE RELATED FINANCIAL TRANSACTION DATAREPRESENTING TWO OR MORE DISCRETE INVOICES SUBMITTED BY ONE OR MOREPAYEE BUSINESSES REQUESTING PAYMENT BY PAYOR USERS OF THE PERSONALFINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 203 includes anymethod, system, process and/or procedure for obtaining access to invoicerelated financial transaction data generated by the one or more payeebusinesses as discussed herein, known in the art at the time of filing,and/or as developed/made available after the time of filing.

In accordance with one embodiment, obtaining access to invoice relatedfinancial transaction data generated by the one or more payee businessesat OBTAIN ACCESS TO INVOICE RELATED FINANCIAL TRANSACTION DATAREPRESENTING TWO OR MORE DISCRETE INVOICES SUBMITTED BY ONE OR MOREPAYEE BUSINESSES REQUESTING PAYMENT BY PAYOR USERS OF THE PERSONALFINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 203 includes anymethod, system, process and/or procedure for obtaining access to invoicerelated financial transaction data generated by the one or more payeebusinesses as discussed in: U.S. patent application Ser. No. 15/140,117(docket number INTU169676), filed on behalf of the same Inventors of thepresent patent application, filed on Apr. 27, 2016, entitled “METHOD ANDSYSTEM FOR PROVIDING INVOICES GENERATED THROUGH A BUSINESS INVOICINGSYSTEM TO A CUSTOMER USER OF A PERSONAL FINANCIAL MANAGEMENT AND BILLPAYMENT SYSTEM,” which is herein incorporated by reference in itsentirety as if it were fully set forth herein; and/or U.S. patentapplication Ser. No. 15/140,131 (docket number INTU169677), filed onbehalf of the same Inventors of the present patent application, filed onApr. 27, 2016, entitled “METHOD AND SYSTEM FOR IDENTIFYING INVOICES THATARE PAID THROUGH A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENTSYSTEM,” which is herein incorporated by reference in its entirety as ifit were fully set forth herein; and/or U.S. patent application Ser. No.15/142,708 (docket number INTU169678), filed on behalf of the sameInventors of the present patent application, filed on Apr. 29, 2016,entitled “METHOD AND SYSTEM FOR INTEGRATING BUSINESS INVOICES INTO APERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM,” which is hereinincorporated by reference in its entirety as if it were fully set forthherein.

In one embodiment once access to invoice related financial transactiondata generated by the one or more payee businesses is obtained at OBTAINACCESS TO INVOICE RELATED FINANCIAL TRANSACTION DATA REPRESENTING TWO ORMORE DISCRETE INVOICES SUBMITTED BY ONE OR MORE PAYEE BUSINESSESREQUESTING PAYMENT BY PAYOR USERS OF THE PERSONAL FINANCIAL MANAGEMENTAND BILL PAYMENT SYSTEM OPERATION 203, process flow proceeds toINTEGRATE THE INVOICE RELATED FINANCIAL TRANSACTION DATA INTO PERSONALFINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM PAYMENT DUE DATA ASSOCIATEDWITH A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION205.

In one embodiment, at INTEGRATE THE INVOICE RELATED FINANCIALTRANSACTION DATA INTO PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENTSYSTEM PAYMENT DUE DATA ASSOCIATED WITH A PERSONAL FINANCIAL MANAGEMENTAND BILL PAYMENT SYSTEM OPERATION 205, the invoice related financialtransaction data of OBTAIN ACCESS TO INVOICE RELATED FINANCIALTRANSACTION DATA REPRESENTING TWO OR MORE DISCRETE INVOICES SUBMITTED BYONE OR MORE PAYEE BUSINESSES REQUESTING PAYMENT BY PAYOR USERS OF THEPERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 203 isintegrated into personal financial management and bill payment systempayment due data associated with a personal financial management andbill payment system.

In one embodiment, a personal financial management and bill paymentsystem is provided using one or more computing systems.

In accordance with one embodiment, at INTEGRATE THE INVOICE RELATEDFINANCIAL TRANSACTION DATA INTO PERSONAL FINANCIAL MANAGEMENT AND BILLPAYMENT SYSTEM PAYMENT DUE DATA ASSOCIATED WITH A PERSONAL FINANCIALMANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 205 the invoice relatedfinancial transaction data is integrated into personal financialmanagement and bill payment system payment due data associated with thepersonal financial management and bill payment system using one or moreprocessors associated with one or more computing systems.

In one embodiment, the personal financial management and bill paymentsystem payment due data represents one or more payments due associatedwith one or more users of the personal financial management and billpayment system as payment due items to be paid through the personalfinancial management and bill payment system.

In accordance with one embodiment, the invoice related financialtransaction data is integrated into personal financial management andbill payment system payment due data associated with a personalfinancial management and bill payment system at INTEGRATE THE INVOICERELATED FINANCIAL TRANSACTION DATA INTO PERSONAL FINANCIAL MANAGEMENTAND BILL PAYMENT SYSTEM PAYMENT DUE DATA ASSOCIATED WITH A PERSONALFINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 205 by assigninga personal financial management and bill payment system financialtransaction category to the discrete invoices represented in the invoicerelated financial transaction data.

In accordance with one embodiment, the invoice related financialtransaction data is integrated into personal financial management andbill payment system payment due data associated with a personalfinancial management and bill payment system at INTEGRATE THE INVOICERELATED FINANCIAL TRANSACTION DATA INTO PERSONAL FINANCIAL MANAGEMENTAND BILL PAYMENT SYSTEM PAYMENT DUE DATA ASSOCIATED WITH A PERSONALFINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 205 by providingthe discrete invoices represented in the invoice related financialtransaction data as line items in a payment due item listing generatedthrough the personal financial management and bill payment system.

In accordance with one embodiment, the invoice related financialtransaction data is integrated into personal financial management andbill payment system payment due data associated with a personalfinancial management and bill payment system at INTEGRATE THE INVOICERELATED FINANCIAL TRANSACTION DATA INTO PERSONAL FINANCIAL MANAGEMENTAND BILL PAYMENT SYSTEM PAYMENT DUE DATA ASSOCIATED WITH A PERSONALFINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 205 by assigninga personal financial management and bill payment system financialtransaction category to the discrete invoices represented in the invoicerelated financial transaction data.

In accordance with one embodiment, the invoice related financialtransaction data is integrated into personal financial management andbill payment system payment due data associated with a personalfinancial management and bill payment system at INTEGRATE THE INVOICERELATED FINANCIAL TRANSACTION DATA INTO PERSONAL FINANCIAL MANAGEMENTAND BILL PAYMENT SYSTEM PAYMENT DUE DATA ASSOCIATED WITH A PERSONALFINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 205 by anymethod, system, process and/or procedure for integrating invoice relatedfinancial transaction data into personal financial management and billpayment system payment due data as discussed herein, known in the art atthe time of filing, and/or as developed/made available after the time offiling.

In accordance with various embodiments, the invoice related financialtransaction data is integrated into personal financial management andbill payment system payment due data associated with a personalfinancial management and bill payment system at INTEGRATE THE INVOICERELATED FINANCIAL TRANSACTION DATA INTO PERSONAL FINANCIAL MANAGEMENTAND BILL PAYMENT SYSTEM PAYMENT DUE DATA ASSOCIATED WITH A PERSONALFINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 205 by anymethod, system, process and/or procedure for integrating invoice relatedfinancial transaction data into personal financial management and billpayment system payment due data as discussed in: U.S. patent applicationSer. No. 15/140,117 (docket number INTU169676), filed on behalf of thesame Inventors of the present patent application, filed on Apr. 27,2016, entitled “METHOD AND SYSTEM FOR PROVIDING INVOICES GENERATEDTHROUGH A BUSINESS INVOICING SYSTEM TO A CUSTOMER USER OF A PERSONALFINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM,” which is hereinincorporated by reference in its entirety as if it were fully set forthherein; and/or U.S. patent application Ser. No. 15/140,131 (docketnumber INTU169677), filed on behalf of the same Inventors of the presentpatent application, filed on Apr. 27, 2016, entitled “METHOD AND SYSTEMFOR IDENTIFYING INVOICES THAT ARE PAID THROUGH A PERSONAL FINANCIALMANAGEMENT AND BILL PAYMENT SYSTEM,” which is herein incorporated byreference in its entirety as if it were fully set forth herein; and/orU.S. patent application Ser. No. 15/142,708 (docket number INTU169678),filed on behalf of the same Inventors of the present patent application,filed on Apr. 29, 2016, entitled “METHOD AND SYSTEM FOR INTEGRATINGBUSINESS INVOICES INTO A PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENTSYSTEM,” which is herein incorporated by reference in its entirety as ifit were fully set forth herein.

In one embodiment, once the invoice related financial transaction datais integrated into personal financial management and bill payment systempayment due data associated with a personal financial management andbill payment system at INTEGRATE THE INVOICE RELATED FINANCIALTRANSACTION DATA INTO PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENTSYSTEM PAYMENT DUE DATA ASSOCIATED WITH A PERSONAL FINANCIAL MANAGEMENTAND BILL PAYMENT SYSTEM OPERATION 205, process flow proceeds to RECEIVEINVOICE PAYMENT REQUEST DATA FROM ONE OR MORE USERS OF THE PERSONALFINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 207.

In one embodiment, at RECEIVE INVOICE PAYMENT REQUEST DATA FROM ONE ORMORE USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEMOPERATION 207, invoice payment request data is received from one or moreusers of the personal financial management and bill payment system.

As noted above, personal financial management and bill payment systemshelp a personal financial management and bill payment system user, orany authorized party acting on behalf of a personal financial managementand bill payment system user, obtain financial transaction datarepresenting financial transactions conducted by the user,process/analyze the financial transaction data, display categorizedfinancial transaction data, generate financial transaction reports,generate bills due and payment due reports, and/or make manual,semi-automated, and/or automatic bill payments through the personalfinancial management and bill payment system.

As also noted above, some personal financial management and bill paymentsystems help users manage their finances and/or track theirexpenditures/financial transactions by providing a centralized interfacewith banks, credit card companies, and various other financialinstitutions, for electronically identifying and categorizing the user'sfinancial transaction data. Currently, personal financial management andbill payment systems typically obtain electronic financial transactiondata, such as payee data, payment amount data, transaction date data,etc. via communication with banks, credit card providers, or otherfinancial institutions, using electronic data transfer systems, orvarious other systems for obtaining/transferring financial transactiondata.

In addition, some personal financial management and bill payment systemsinclude a payment due report/display generation feature. Typically, apayment due report includes personal financial management and billpayment system payment due data representing a listing of payments due,e.g., bill payment due items, within a defined period of time, such as amonth, which require the user's attention.

As also noted above, in some cases, the users of the personal financialmanagement and bill payment systems are also provided a bill paymentservice and the capability to make payments on a manual, semi-automatic,i.e., with user approval, or automatic, basis to various payees. Inorder to make these payments, the users of the personal financialmanagement and bill payment systems typically enter data into thepersonal financial management and bill payment systems directing, orrequesting, that one or more payments be made to one or more payees on aone-time, recurring, automatic, semi-automatic, or manual basis.

In the present embodiments, where invoice related financial transactiondata has been integrated into the personal financial management and billpayment system payment due data at INTEGRATE THE INVOICE RELATEDFINANCIAL TRANSACTION DATA INTO PERSONAL FINANCIAL MANAGEMENT AND BILLPAYMENT SYSTEM PAYMENT DUE DATA ASSOCIATED WITH A PERSONAL FINANCIALMANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 205, invoice paymentrequests are made by the users of the personal financial management andbill payment systems by entering, and/or providing, invoice paymentrequest data.

In one embodiment, the invoice payment request data received by thepersonal financial management and bill payment system at RECEIVE INVOICEPAYMENT REQUEST DATA FROM ONE OR MORE USERS OF THE PERSONAL FINANCIALMANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 207 represents one or morerequests from one or more users of the personal financial management andbill payment system to pay one or more requested invoice payment amountsassociated with one or more discrete invoice payment request relatedinvoices represented in the invoice related financial transaction datathrough the personal financial management and bill payment system.

In one embodiment, once invoice payment request data is received fromone or more users of the personal financial management and bill paymentsystem at RECEIVE INVOICE PAYMENT REQUEST DATA FROM ONE OR MORE USERS OFTHE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 207,process flow proceeds to OBTAIN ACCESS TO THE PERSONAL FINANCIALMANAGEMENT AND BILL PAYMENT SYSTEM PAYMENT DUE DATA, INCLUDING THEINTEGRATED INVOICE RELATED FINANCIAL TRANSACTION DATA, AND THE INVOICEPAYMENT REQUEST DATA OPERATION 209.

In one embodiment, at OBTAIN ACCESS TO THE PERSONAL FINANCIAL MANAGEMENTAND BILL PAYMENT SYSTEM PAYMENT DUE DATA, INCLUDING THE INTEGRATEDINVOICE RELATED FINANCIAL TRANSACTION DATA, AND THE INVOICE PAYMENTREQUEST DATA OPERATION 209, access to the personal financial managementand bill payment system and the personal financial management and billpayment system payment due data, including the integrated invoicerelated financial transaction data, of INTEGRATE THE INVOICE RELATEDFINANCIAL TRANSACTION DATA INTO PERSONAL FINANCIAL MANAGEMENT AND BILLPAYMENT SYSTEM PAYMENT DUE DATA ASSOCIATED WITH A PERSONAL FINANCIALMANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 205, and the invoicepayment request data of RECEIVE INVOICE PAYMENT REQUEST DATA FROM ONE ORMORE USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEMOPERATION 207 is obtained.

In accordance with one embodiment, one or more processors associatedwith one or more computing systems are utilized to obtain access to thepersonal financial management and bill payment system and the personalfinancial management and bill payment system payment due data, includingthe integrated invoice related financial transaction data, and theinvoice payment request data at OBTAIN ACCESS TO THE PERSONAL FINANCIALMANAGEMENT AND BILL PAYMENT SYSTEM PAYMENT DUE DATA, INCLUDING THEINTEGRATED INVOICE RELATED FINANCIAL TRANSACTION DATA, AND THE INVOICEPAYMENT REQUEST DATA OPERATION 209.

In one embodiment, once access to the personal financial management andbill payment system and the personal financial management and billpayment system payment due data, including the integrated invoicerelated financial transaction data, and the invoice payment request datais obtained at OBTAIN ACCESS TO THE PERSONAL FINANCIAL MANAGEMENT ANDBILL PAYMENT SYSTEM PAYMENT DUE DATA, INCLUDING THE INTEGRATED INVOICERELATED FINANCIAL TRANSACTION DATA, AND THE INVOICE PAYMENT REQUEST DATAOPERATION 209, process flow proceeds to ANALYZE THE INVOICE PAYMENTREQUEST DATA TO IDENTIFY DISCRETE INVOICE PAYMENT REQUEST RELATEDINVOICE DATA OPERATION 211.

In one embodiment, at ANALYZE THE INVOICE PAYMENT REQUEST DATA TOIDENTIFY DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICE DATA OPERATION211, the invoice payment request data of RECEIVE INVOICE PAYMENT REQUESTDATA FROM ONE OR MORE USERS OF THE PERSONAL FINANCIAL MANAGEMENT ANDBILL PAYMENT SYSTEM OPERATION 207 is analyzed by to identify discreteinvoice payment request related invoice data representing one or morediscrete invoice payment request related invoices represented in theinvoice related financial transaction data.

In one embodiment, at ANALYZE THE INVOICE PAYMENT REQUEST DATA TOIDENTIFY DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICE DATA OPERATION211, the invoice payment request data is analyzed by one or moreprocessors associated with one or more computing systems to identifydiscrete invoice payment request related invoice data representing oneor more discrete invoice payment request related invoices represented inthe invoice related financial transaction data.

In one embodiment, once the invoice payment request data is analyzed toidentify discrete invoice payment request related invoice datarepresenting one or more discrete invoice payment request relatedinvoices represented in the invoice related financial transaction dataat ANALYZE THE INVOICE PAYMENT REQUEST DATA TO IDENTIFY DISCRETE INVOICEPAYMENT REQUEST RELATED INVOICE DATA OPERATION 211, process flowproceeds to IDENTIFY A FIRST PAYEE BUSINESS REPRESENTED IN THE PAYEEBUSINESS IDENTITY DATA ASSOCIATED WITH TWO OR MORE DISCRETE FIRST PAYEEBUSINESS INVOICE PAYMENT REQUEST RELATED INVOICES REPRESENTED IN THEDISCRETE INVOICE PAYMENT REQUEST RELATED INVOICE DATA OPERATION 213.

In one embodiment, at IDENTIFY A FIRST PAYEE BUSINESS REPRESENTED IN THEPAYEE BUSINESS IDENTITY DATA ASSOCIATED WITH TWO OR MORE DISCRETE FIRSTPAYEE BUSINESS INVOICE PAYMENT REQUEST RELATED INVOICES REPRESENTED INTHE DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICE DATA OPERATION 213,the integrated invoice related financial transaction data associatedwith the discrete invoice payment request related invoices of ANALYZETHE INVOICE PAYMENT REQUEST DATA TO IDENTIFY DISCRETE INVOICE PAYMENTREQUEST RELATED INVOICE DATA OPERATION 211 is analyzed to identify thepayee business identity data associated with each discrete invoicepayment request related invoice represented in the discrete invoicepayment request related invoice data and a first payee businessrepresented in the payee business identity data associated with two ormore discrete first payee business invoice payment request relatedinvoices represented in the discrete invoice payment request relatedinvoice data is identified.

In one embodiment, at IDENTIFY A FIRST PAYEE BUSINESS REPRESENTED IN THEPAYEE BUSINESS IDENTITY DATA ASSOCIATED WITH TWO OR MORE DISCRETE FIRSTPAYEE BUSINESS INVOICE PAYMENT REQUEST RELATED INVOICES REPRESENTED INTHE DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICE DATA OPERATION 213,the integrated invoice related financial transaction data associatedwith the discrete invoice payment request related invoices is analyzedby one or more processors associated with one or more computing systemsto identify the payee business identity data associated with eachdiscrete invoice payment request related invoice represented in thediscrete invoice payment request related invoice data and a first payeebusiness represented in the payee business identity data associated withtwo or more discrete first payee business invoice payment requestrelated invoices represented in the discrete invoice payment requestrelated invoice data is identified.

In one embodiment, once a first payee business represented in the payeebusiness identity data associated with two or more discrete first payeebusiness invoice payment request related invoices represented in thediscrete invoice payment request related invoice data is identified atIDENTIFY A FIRST PAYEE BUSINESS REPRESENTED IN THE PAYEE BUSINESSIDENTITY DATA ASSOCIATED WITH TWO OR MORE DISCRETE FIRST PAYEE BUSINESSINVOICE PAYMENT REQUEST RELATED INVOICES REPRESENTED IN THE DISCRETEINVOICE PAYMENT REQUEST RELATED INVOICE DATA OPERATION 213, process flowproceeds to AGGREGATE ALL THE INVOICE RELATED FINANCIAL TRANSACTION DATAASSOCIATED WITH THE TWO OR MORE DISCRETE INVOICE PAYMENT REQUEST RELATEDINVOICES TO GENERATE AGGREGATED FIRST PAYEE BUSINESS INVOICE PAYMENTREQUEST INVOICE DATA OPERATION 215.

In one embodiment, at AGGREGATE ALL THE INVOICE RELATED FINANCIALTRANSACTION DATA ASSOCIATED WITH THE TWO OR MORE DISCRETE INVOICEPAYMENT REQUEST RELATED INVOICES TO GENERATE AGGREGATED FIRST PAYEEBUSINESS INVOICE PAYMENT REQUEST INVOICE DATA OPERATION 215, all theinvoice related financial transaction data associated with the two ormore discrete invoice payment request related invoices of IDENTIFY AFIRST PAYEE BUSINESS REPRESENTED IN THE PAYEE BUSINESS IDENTITY DATAASSOCIATED WITH TWO OR MORE DISCRETE FIRST PAYEE BUSINESS INVOICEPAYMENT REQUEST RELATED INVOICES REPRESENTED IN THE DISCRETE INVOICEPAYMENT REQUEST RELATED INVOICE DATA OPERATION 213 is aggregated togenerate aggregated first payee business invoice payment request invoicedata.

In one embodiment, at AGGREGATE ALL THE INVOICE RELATED FINANCIALTRANSACTION DATA ASSOCIATED WITH THE TWO OR MORE DISCRETE INVOICEPAYMENT REQUEST RELATED INVOICES TO GENERATE AGGREGATED FIRST PAYEEBUSINESS INVOICE PAYMENT REQUEST INVOICE DATA OPERATION 215, all theinvoice related financial transaction data associated with the two ormore discrete invoice payment request related invoices is aggregated byone or more processors associated with one or more computing systems togenerate aggregated first payee business invoice payment request invoicedata.

In one embodiment, once all the invoice related financial transactiondata associated with the two or more discrete invoice payment requestrelated invoices is aggregated to generate aggregated first payeebusiness invoice payment request invoice data at AGGREGATE ALL THEINVOICE RELATED FINANCIAL TRANSACTION DATA ASSOCIATED WITH THE TWO ORMORE DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICES TO GENERATEAGGREGATED FIRST PAYEE BUSINESS INVOICE PAYMENT REQUEST INVOICE DATAOPERATION 215, process flow proceeds to ANALYZE THE AGGREGATED FIRSTPAYEE BUSINESS INVOICE PAYMENT REQUEST INVOICE DATA TO IDENTIFY THEREQUESTED INVOICE PAYMENT AMOUNT DATA ASSOCIATED WITH EACH OF THE TWO ORMORE DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICES OPERATION 217.

In one embodiment, at ANALYZE THE AGGREGATED FIRST PAYEE BUSINESSINVOICE PAYMENT REQUEST INVOICE DATA TO IDENTIFY THE REQUESTED INVOICEPAYMENT AMOUNT DATA ASSOCIATED WITH EACH OF THE TWO OR MORE DISCRETEINVOICE PAYMENT REQUEST RELATED INVOICES OPERATION 217, the aggregatedfirst payee business invoice payment request invoice data of AGGREGATEALL THE INVOICE RELATED FINANCIAL TRANSACTION DATA ASSOCIATED WITH THETWO OR MORE DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICES TOGENERATE AGGREGATED FIRST PAYEE BUSINESS INVOICE PAYMENT REQUEST INVOICEDATA OPERATION 215 is analyzed to identify the requested invoice paymentamount data associated with each of the two or more discrete invoicepayment request related invoices.

In one embodiment, at ANALYZE THE AGGREGATED FIRST PAYEE BUSINESSINVOICE PAYMENT REQUEST INVOICE DATA TO IDENTIFY THE REQUESTED INVOICEPAYMENT AMOUNT DATA ASSOCIATED WITH EACH OF THE TWO OR MORE DISCRETEINVOICE PAYMENT REQUEST RELATED INVOICES OPERATION 217, the aggregatedfirst payee business invoice payment request invoice data is analyzed byone or more processors associated with one or more computing systems toidentify the requested invoice payment amount data associated with eachof the two or more discrete invoice payment request related invoices.

In one embodiment, once the aggregated first payee business invoicepayment request invoice data is analyzed to identify the requestedinvoice payment amount data associated with each of the two or morediscrete invoice payment request related invoices at ANALYZE THEAGGREGATED FIRST PAYEE BUSINESS INVOICE PAYMENT REQUEST INVOICE DATA TOIDENTIFY THE REQUESTED INVOICE PAYMENT AMOUNT DATA ASSOCIATED WITH EACHOF THE TWO OR MORE DISCRETE INVOICE PAYMENT REQUEST RELATED INVOICESOPERATION 217, process flow proceeds to GENERATE AGGREGATED TOTAL FIRSTPAYEE BUSINESS INVOICE PAYMENT AMOUNT DATA REPRESENTING A TOTALREQUESTED INVOICE PAYMENT AMOUNT FOR THE FIRST PAYEE BUSINESS REQUESTEDBY TWO OR MORE USERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILLPAYMENT SYSTEM OPERATION 219.

In one embodiment, at GENERATE AGGREGATED TOTAL FIRST PAYEE BUSINESSINVOICE PAYMENT AMOUNT DATA REPRESENTING A TOTAL REQUESTED INVOICEPAYMENT AMOUNT FOR THE FIRST PAYEE BUSINESS REQUESTED BY TWO OR MOREUSERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEMOPERATION 219, the requested invoice payment amount data associated witheach of the two or more discrete invoice payment request relatedinvoices of ANALYZE THE AGGREGATED FIRST PAYEE BUSINESS INVOICE PAYMENTREQUEST INVOICE DATA TO IDENTIFY THE REQUESTED INVOICE PAYMENT AMOUNTDATA ASSOCIATED WITH EACH OF THE TWO OR MORE DISCRETE INVOICE PAYMENTREQUEST RELATED INVOICES OPERATION 217 is processed and summed togenerate aggregated total first payee business invoice payment amountdata representing a total requested invoice payment amount for the firstpayee business as requested by two or more users of the personalfinancial management and bill payment system.

In one embodiment, at GENERATE AGGREGATED TOTAL FIRST PAYEE BUSINESSINVOICE PAYMENT AMOUNT DATA REPRESENTING A TOTAL REQUESTED INVOICEPAYMENT AMOUNT FOR THE FIRST PAYEE BUSINESS REQUESTED BY TWO OR MOREUSERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEMOPERATION 219, the requested invoice payment amount data associated witheach of the two or more discrete invoice payment request relatedinvoices is processed and summed by one or more processors associatedwith one or more computing systems to generate aggregated total firstpayee business invoice payment amount data representing a totalrequested invoice payment amount for the first payee business requestedby two or more users of the personal financial management and billpayment system.

In one embodiment, once the requested invoice payment amount dataassociated with each of the two or more discrete invoice payment requestrelated invoices is processed and summed to generate aggregated totalfirst payee business invoice payment amount data representing a totalrequested invoice payment amount for the first payee business asrequested by two or more users of the personal financial management andbill payment system at GENERATE AGGREGATED TOTAL FIRST PAYEE BUSINESSINVOICE PAYMENT AMOUNT DATA REPRESENTING A TOTAL REQUESTED INVOICEPAYMENT AMOUNT FOR THE FIRST PAYEE BUSINESS REQUESTED BY TWO OR MOREUSERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEMOPERATION 219, process flow proceeds to PROCESS THE AGGREGATED TOTALFIRST PAYEE BUSINESS INVOICE PAYMENT AMOUNT DATA AS A SINGLE FIRST PAYEEBUSINESS FUNDS TRANSFER ITEM USING THE PERSONAL FINANCIAL MANAGEMENT ANDBILL PAYMENT SYSTEM OPERATION 221.

In one embodiment, at PROCESS THE AGGREGATED TOTAL FIRST PAYEE BUSINESSINVOICE PAYMENT AMOUNT DATA AS A SINGLE FIRST PAYEE BUSINESS FUNDSTRANSFER ITEM USING THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENTSYSTEM OPERATION 221, the aggregated total first payee business invoicepayment amount data of GENERATE AGGREGATED TOTAL FIRST PAYEE BUSINESSINVOICE PAYMENT AMOUNT DATA REPRESENTING A TOTAL REQUESTED INVOICEPAYMENT AMOUNT FOR THE FIRST PAYEE BUSINESS REQUESTED BY TWO OR MOREUSERS OF THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEMOPERATION 219 is processed as a single first payee business fundstransfer item using the personal financial management and bill paymentsystem.

In one embodiment, at PROCESS THE AGGREGATED TOTAL FIRST PAYEE BUSINESSINVOICE PAYMENT AMOUNT DATA AS A SINGLE FIRST PAYEE BUSINESS FUNDSTRANSFER ITEM USING THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENTSYSTEM OPERATION 221, the aggregated total first payee business invoicepayment amount data is processed by one or more processors associatedwith one or more computing systems as a single first payee businessfunds transfer item using the personal financial management and billpayment system.

In accordance with one embodiment, processing the aggregated total firstpayee business invoice payment amount data as a single first payeebusiness funds transfer item using the personal financial management andbill payment system at PROCESS THE AGGREGATED TOTAL FIRST PAYEE BUSINESSINVOICE PAYMENT AMOUNT DATA AS A SINGLE FIRST PAYEE BUSINESS FUNDSTRANSFER ITEM USING THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENTSYSTEM OPERATION 221 includes providing the aggregated total first payeebusiness invoice payment amount data as a line item in a funds transferitem listing generated through the personal financial management andbill payment system.

In accordance with one embodiment, processing the aggregated total firstpayee business invoice payment amount data as a single first payeebusiness funds transfer item using the personal financial management andbill payment system at PROCESS THE AGGREGATED TOTAL FIRST PAYEE BUSINESSINVOICE PAYMENT AMOUNT DATA AS A SINGLE FIRST PAYEE BUSINESS FUNDSTRANSFER ITEM USING THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENTSYSTEM OPERATION 221 includes applying one or more aggregated firstpayee business invoice payment request invoice data processing rules tothe aggregated first payee business invoice payment request invoicedata.

In accordance with one embodiment, the aggregated first payee businessinvoice payment request invoice data processing rules of PROCESS THEAGGREGATED TOTAL FIRST PAYEE BUSINESS INVOICE PAYMENT AMOUNT DATA AS ASINGLE FIRST PAYEE BUSINESS FUNDS TRANSFER ITEM USING THE PERSONALFINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 221 include, butare not limited to, an aggregated first payee business invoice paymentrequest invoice data processing rule limiting the aggregated total firstpayee business invoice payment amount to a threshold amount.

Using this aggregated first payee business invoice payment requestinvoice data processing rule, the financial risk associated with thesingle first payee business funds transfer transaction is limited to thethreshold amount.

In accordance with one embodiment, the aggregated first payee businessinvoice payment request invoice data processing rules of PROCESS THEAGGREGATED TOTAL FIRST PAYEE BUSINESS INVOICE PAYMENT AMOUNT DATA AS ASINGLE FIRST PAYEE BUSINESS FUNDS TRANSFER ITEM USING THE PERSONALFINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 221 include, butare not limited to, an aggregated first payee business invoice paymentrequest invoice data processing rule limiting the total number ofdiscrete invoices represented in the aggregated first payee businessinvoice payment request invoice data to a threshold number of discreteinvoices.

Using this aggregated first payee business invoice payment requestinvoice data processing rule, the total liability associated with thesingle first payee business funds transfer transaction is limited to atotal aggregated invoice amount associated with a threshold number ofdiscrete invoices, thereby limiting the financial risk.

In accordance with one embodiment, the aggregated first payee businessinvoice payment request invoice data processing rules of PROCESS THEAGGREGATED TOTAL FIRST PAYEE BUSINESS INVOICE PAYMENT AMOUNT DATA AS ASINGLE FIRST PAYEE BUSINESS FUNDS TRANSFER ITEM USING THE PERSONALFINANCIAL MANAGEMENT AND BILL PAYMENT SYSTEM OPERATION 221 include anythe aggregated first payee business invoice payment request invoice dataprocessing rules desired, and/or as discussed herein, known in the artat the time of filing, and/or as developed/made available after the timeof filing.

In one embodiment, once the aggregated total first payee businessinvoice payment amount data is then processed as a single first payeebusiness funds transfer item using the personal financial management andbill payment system at PROCESS THE AGGREGATED TOTAL FIRST PAYEE BUSINESSINVOICE PAYMENT AMOUNT DATA AS A SINGLE FIRST PAYEE BUSINESS FUNDSTRANSFER ITEM USING THE PERSONAL FINANCIAL MANAGEMENT AND BILL PAYMENTSYSTEM OPERATION 221, process flow proceeds to EXIT OPERATION 230.

In one embodiment, at EXIT OPERATION 230, process 200 for integratingdiscrete invoices into a personal financial management and bill paymentsystem and then aggregating discrete invoices having the same payeebusiness into a single funds transfer transaction is exited to await newdata.

The disclosed embodiments of process 200 for integrating discreteinvoices into a personal financial management and bill payment systemand then aggregating discrete invoices having the same payee businessinto a single funds transfer transaction provide an efficient,effective, and highly adaptable solution to the long standing technicalproblem in the bill payment, invoice processing, and financialmanagement arts of automatically integrating invoice related financialtransaction data into a personal financial management and bill paymentsystem, and/or identifying, or distinguishing, invoice related financialtransaction data, and then aggregating requested invoice payment amountsassociated with invoices represented in the invoice related financialtransaction data having the same payee business into a single fundstransfer transaction item to be processed by the personal financialmanagement and bill payment system.

However, the disclosed process 200 for integrating discrete invoicesinto a personal financial management and bill payment system and thenaggregating discrete invoices having the same payee business into asingle funds transfer transaction does not encompass, embody, orpreclude other forms of innovation in the area of automated financialtransaction bill payment processing and invoicing. In addition, theprocess 200 for integrating discrete invoices into a personal financialmanagement and bill payment system and then aggregating discreteinvoices having the same payee business into a single funds transfertransaction is not related to any fundamental economic practice,fundamental data processing practice, mental steps, or pen and paperbased solution. In fact, the disclosed embodiments are directed toproviding solutions to the relatively new problems associated with theautomatic processing and display of electronic financial transactiondata obtained from multiple sources, making electronic bill payments,and the management and processing of large amounts of data, i.e., “bigdata.” Consequently, the disclosed process 200 for integrating discreteinvoices into a personal financial management and bill payment systemand then aggregating discrete invoices having the same payee businessinto a single funds transfer transaction is not directed to, does notencompass, and is not merely, an abstract idea or concept.

In addition, the disclosed process 200 for integrating discrete invoicesinto a personal financial management and bill payment system and thenaggregating discrete invoices having the same payee business into asingle funds transfer transaction provides for significant improvementsto the technical fields of electronic transaction data processing,invoicing, financial transaction categorization, informationdissemination, data processing, data management, data filtering andmining, automatic electronic bill payment, and user experience.

In addition, by allowing for the integration of invoices and invoicedata into a personal financial management and bill payment system, thedisclosed process 200 for integrating discrete invoices into a personalfinancial management and bill payment system and then aggregatingdiscrete invoices having the same payee business into a single fundstransfer transaction helps users of the personal financial managementand bill payment system identify and pay their invoices. This, in turn,helps avoid the reissuance and repeated transmission of payment duereminders and for the entry, processing, and dissemination, of redundantinvoice data; thereby eliminating unnecessary data analysis beforeresources are allocated to processing, and/or correcting, redundantreminder data and the redundant reminder data is furthertransmitted/distributed.

Consequently, using the disclosed process 200 for integrating discreteinvoices into a personal financial management and bill payment systemand then aggregating discrete invoices having the same payee businessinto a single funds transfer transaction results in more efficient useof human and non-human resources, fewer processor cycles being utilized,reduced memory utilization, and less communications bandwidth beingutilized to relay data to, and from, backend systems and client systems.

As a result, computing systems are transformed into faster, moreefficient, and more effective computing systems by implementing process200 for integrating discrete invoices into a personal financialmanagement and bill payment system and then aggregating discreteinvoices having the same payee business into a single funds transfertransaction.

In addition, the disclosed process 200 for integrating discrete invoicesinto a personal financial management and bill payment system and thenaggregating discrete invoices having the same payee business into asingle funds transfer transaction provides for the entry, processing,and dissemination, of only relevant portions of data; therebyeliminating unnecessary data analysis and correction before resourcesare allocated to processing, and/or correcting, faulty/irrelevant data,and/or the faulty/irrelevant data is further transmitted/distributed.

In addition, by aggregating requested invoice payment amounts associatedwith multiple invoices represented in the invoice related financialtransaction data having the same payee business into single fundstransfer item, the disclosed process 200 for integrating discreteinvoices into a personal financial management and bill payment systemand then aggregating discrete invoices having the same payee businessinto a single funds transfer transaction provides for the processing anddissemination of invoice related financial transaction data representingmultiple discrete invoices as a single funds transfer entity/object.This, in turn, helps avoid the processing and transmission of multipleindividual invoice payment related data sets and related funds transfertransaction data sets.

Consequently, using process 200 for integrating discrete invoices into apersonal financial management and bill payment system and thenaggregating discrete invoices having the same payee business into asingle funds transfer transaction results in more efficient use of humanand non-human resources, fewer processor cycles being utilized, reducedmemory utilization, and less communications bandwidth being utilized torelay data to, and from, backend systems and client systems.

As a result, computing systems are transformed into faster, moreefficient, and more effective computing systems by implementing process200 for integrating discrete invoices into a personal financialmanagement and bill payment system and then aggregating discreteinvoices having the same payee business into a single funds transfertransaction.

The present invention has been described in particular detail withrespect to specific possible embodiments. Those of skill in the art willappreciate that the invention may be practiced in other embodiments. Forexample, the nomenclature used for components, capitalization ofcomponent designations and terms, the attributes, data structures, orany other programming or structural aspect is not significant,mandatory, or limiting, and the mechanisms that implement the inventionor its features can have various different names, formats, and/orprotocols. Further, the system and/or functionality of the invention maybe implemented via various combinations of software and hardware, asdescribed, or entirely in hardware elements. Also, particular divisionsof functionality between the various components described herein, aremerely exemplary, and not mandatory or significant. Consequently,functions performed by a single component may, in other embodiments, beperformed by multiple components, and functions performed by multiplecomponents may, in other embodiments, be performed by a singlecomponent.

Some portions of the above description present the features of thepresent invention in terms of algorithms and symbolic representations ofoperations, or algorithm-like representations, of operations oninformation/data. These algorithmic and/or algorithm-like descriptionsand representations are the mechanism and/or process used by those ofskill in the art to most effectively and efficiently convey thesubstance of their work to others of skill in the art. These operations,while described functionally or logically, are understood to beimplemented by computer programs and/or computing systems. Furthermore,it has also proven convenient at times to refer to these arrangements ofoperations as steps or modules or by functional names, without loss ofgenerality.

Unless specifically stated otherwise, as would be apparent from theabove discussion, it is appreciated that throughout the abovedescription, discussions utilizing terms such as “integrating,”“generating,” “monitoring,” “determining,” “defining,” “designating,”“obtaining,” “accessing,” “analyzing,” “obtaining,” “identifying,”“designating,” categorizing,” “receiving,” “transmitting,”“implementing,” “associating,” “aggregating,” “initiating,”“collecting,” “creating,” “transferring,” “storing,” “searching,”“comparing,” “providing,” “transforming,” “incorporating.” “processing”etc., refer to the action and processes of a computing system or similarelectronic device that manipulates and operates on data represented asphysical (electronic) quantities within the computing system memories,resisters, caches or other information storage, transmission or displaydevices.

Certain aspects of the present invention include process steps oroperations and instructions described herein in an algorithmic and/oralgorithmic-like form. It should be noted that the process steps and/oroperations and instructions of the present invention can be embodied insoftware, firmware, and/or hardware, and when embodied in software, canbe downloaded to reside on and be operated from different platforms usedby real time network operating systems.

The present invention also relates to an apparatus or system forperforming the operations described herein. This apparatus or system maybe specifically constructed for the required purposes by a computerprogram stored via a computer program product as defined herein that canbe accessed by a computing system or other device to transform thecomputing system or other device into a specifically and speciallyprogrammed computing system or other device.

Those of skill in the art will readily recognize that the algorithms andoperations presented herein are not inherently related to any particularcomputing system, computer architecture, computer or industry standard,or any other specific apparatus. It may prove convenient/efficient toconstruct or transform one or more specialized apparatuses to performthe required operations described herein. The required structure for avariety of these systems will be apparent to those of skill in the art,along with equivalent variations. In addition, the present invention isnot described with reference to any particular programming language andit is appreciated that a variety of programming languages may be used toimplement the teachings of the present invention as described herein,and any references to a specific language or languages are provided forillustrative purposes only and for enablement of the contemplated bestmode of the invention at the time of filing.

The present invention is well suited to a wide variety of computernetwork systems operating over numerous topologies. Within this field,the configuration and management of large networks comprise storagedevices and computers that are communicatively coupled to similar and/ordissimilar computers and storage devices over a private network, a LAN,a WAN, a private network, or a public network, such as the Internet.

It should also be noted that the language used in the specification hasbeen principally selected for readability, clarity, and instructionalpurposes, and may not have been selected to delineate or circumscribethe inventive subject matter. Accordingly, the disclosure of the presentinvention is intended to be illustrative, but not limiting, of the scopeof the invention, which is set forth in the claims below.

In addition, the operations shown in the FIG.s are identified using aparticular nomenclature for ease of description and understanding, butother nomenclature is often used in the art to identify equivalentoperations.

In the discussion above, certain aspects of one embodiment includeprocess steps and/or operations and/or instructions described herein forillustrative purposes in a particular order and/or grouping. However,the particular order and/or grouping shown and discussed herein isillustrative only and not limiting. Those of skill in the art willrecognize that other orders and/or grouping of the process steps and/oroperations and/or instructions are possible and, in some embodiments,one or more of the process steps and/or operations and/or instructionsdiscussed above can be combined and/or deleted. In addition, portions ofone or more of the process steps and/or operations and/or instructionscan be re-grouped as portions of one or more other of the process stepsand/or operations and/or instructions discussed herein. Consequently,the particular order and/or grouping of the process steps and/oroperations and/or instructions discussed herein does not limit the scopeof the invention as claimed below.

Therefore, numerous variations, whether explicitly provided for by thespecification or implied by the specification or not, may be implementedby one of skill in the art in view of this disclosure.

What is claimed is:
 1. A method for integrating discrete invoices into apersonal financial management and bill payment system and thenaggregating discrete invoices having the same payee business into asingle funds transfer transaction, the method comprising: obtainingaccess to invoice related financial transaction data generated by theone or more payee businesses, the invoice related financial transactiondata representing two or more discrete invoices submitted by one or morepayee businesses requesting payment by one or more payor users of thepersonal financial management and bill payment system, the invoicerelated financial transaction data including: payee business identitydata associated with each discrete invoice represented in the invoicerelated financial transaction data, the payee business identity datarepresenting the identity of the payee business associated with eachdiscrete invoice represented in the invoice related financialtransaction data; payor user identity data associated with each discreteinvoice represented in the invoice related financial transaction data,the payor user identity data representing the identity of the payor userassociated with each discrete invoice represented in the invoice relatedfinancial transaction data; and invoice amount data associated with eachdiscrete invoice represented in the invoice related financialtransaction data, the invoice amount data representing the paymentamount associated with each discrete invoice represented in the invoicerelated financial transaction data; integrating the invoice relatedfinancial transaction data into personal financial management and billpayment system payment due data associated with a personal financialmanagement and bill payment system, the personal financial managementand bill payment system payment due data representing one or more billsassociated with one or more users of the personal financial managementand bill payment system to be paid through the personal financialmanagement and bill payment system; receiving invoice payment requestdata from one or more users of the personal financial management andbill payment system, the invoice payment request data representing oneor more requests from one or more users of the personal financialmanagement and bill payment system to pay one or more requested invoicepayment amounts associated with one or more discrete invoice paymentrequest related invoices represented in the invoice related financialtransaction data through the personal financial management and billpayment system; obtaining access to the personal financial managementand bill payment system; obtaining access to the personal financialmanagement and bill payment system payment due data, including theintegrated invoice related financial transaction data; obtaining accessto the invoice payment request data; analyzing the invoice paymentrequest data to identify discrete invoice payment request relatedinvoice data representing one or more discrete invoice payment requestrelated invoices represented in the invoice related financialtransaction data; analyzing the integrated invoice related financialtransaction data associated with the discrete invoice payment requestrelated invoices to identify the payee business identity data associatedwith each discrete invoice payment request related invoice representedin the discrete invoice payment request related invoice data;identifying a first payee business represented in the payee businessidentity data associated with two or more discrete first payee businessinvoice payment request related invoices represented in the discreteinvoice payment request related invoice data; aggregating all theinvoice related financial transaction data associated with the two ormore discrete invoice payment request related invoices to generateaggregated first payee business invoice payment request invoice data;analyzing the aggregated first payee business invoice payment requestinvoice data to identify the requested invoice payment amount dataassociated with each of the two or more discrete invoice payment requestrelated invoices; adding the requested invoice payment amount dataassociated with each of the two or more discrete invoice payment requestrelated invoices to generate aggregated total first payee businessinvoice payment amount data representing a total requested invoicepayment amount for the first payee business requested by two or moreusers of the personal financial management and bill payment system; andprocessing the aggregated total first payee business invoice paymentamount data as a single first payee business funds transfer item usingthe personal financial management and bill payment system.
 2. The methodfor integrating discrete invoices into a personal financial managementand bill payment system and then aggregating discrete invoices havingthe same payee business into a single funds transfer transaction ofclaim 1 wherein obtaining access to invoice related financialtransaction data generated by the one or more payee businesses includes:obtaining access to personal financial management and bill paymentsystem user financial transaction data associated with the personalfinancial management and bill payment system, the personal financialmanagement and bill payment system user financial transaction datarepresenting financial transactions associated with users of a personalfinancial management and bill payment system; analyzing the personalfinancial management and bill payment system user financial transactiondata associated with the first payor user to identify payee dataincluded in the financial transaction data associated with a first payoruser, the payee data representing one or more payees associated withfirst payor user financial transactions associated with the first payoruser represented by a portion of the personal financial management andbill payment system user financial transaction data associated with thefirst payor user; obtaining access to business invoicing system businessuser identification data associated with a business invoicing system,the business user identification data representing business users of thebusiness invoicing system; accessing the payee data and the businessuser identification data and analyzing the payee data and business useridentification data to determine if a payee represented in the payeedata matches a business user of the business invoicing systemrepresented in the business user identification data; identifying apayee represented in the payee data that matches a business user of thebusiness invoicing system represented in the business useridentification data, the payee being a payee associated with firstfinancial transaction data representing a first financial transactionincluded in the personal financial management and bill payment systemuser financial transaction data associated with the first payor user;designating the payee represented in the payee data that matches thebusiness user of the business invoicing system as a first payeebusiness; transforming status data associated with the first financialtransaction data representing the first financial transaction to firstinvoice related financial transaction data; processing the first invoicerelated financial transaction data as invoice related financialtransaction data; and providing the first payee business the capabilityto provide invoicing data representing invoices generated by first payeebusiness to the first payor user of the personal financial managementand bill payment system through the personal financial management andbill payment system.
 3. The method for integrating discrete invoicesinto a personal financial management and bill payment system and thenaggregating discrete invoices having the same payee business into asingle funds transfer transaction of claim 1 wherein obtaining access toinvoice related financial transaction data generated by the one or morepayee businesses includes: obtaining access to personal financialmanagement and bill payment system user identification data associatedwith users of a personal financial management and bill payment system;obtaining access to invoicing data generated through a businessinvoicing system, the invoicing data representing invoices sent frompayee business users of the business invoicing system to payor customersof the payee business users of the business invoicing system; monitoringthe invoicing data and identifying first invoice data representing aninvoice generated by a first payee business user of the businessinvoicing system associated with a first payor customer of the firstpayee business user of the business invoicing system; analyzing thefirst invoice data to identify first payor customer identification dataassociated with the first payor customer of the first payee businessuser of the business invoicing system; analyzing the personal financialmanagement and bill payment system user identification data and thefirst payor customer identification data to determine if the first payorcustomer associated with the first payor customer identification data isa first payor user of the personal financial management and bill paymentsystem; and if a determination is made that the first payor customerassociated with the first payor customer identification data is a firstpayor user of the personal financial management and bill payment system,designating the first payor customer as a first payor user of thepersonal financial management and bill payment system; providing thefirst payee business user of the business invoicing system thecapability to provide invoicing data representing invoices generated bythe first payee business user of the business invoicing system to thefirst payor user of the personal financial management and bill paymentsystem through the personal financial management and bill paymentsystem.
 4. The method for integrating discrete invoices into a personalfinancial management and bill payment system and then aggregatingdiscrete invoices having the same payee business into a single fundstransfer transaction of claim 1 wherein obtaining access to invoicerelated financial transaction data generated by the one or more payeebusinesses includes: obtaining access to personal financial managementand bill payment system user identification data associated with usersof a personal financial management and bill payment system; obtainingaccess to business invoicing system payor customer identification datagenerated through a business invoicing system, the business invoicingsystem payor customer identification data being associated with payorcustomers of user payee businesses of a business invoicing system;analyzing the personal financial management and bill payment system useridentification data and the business invoicing system payor customeridentification data to identify payor users of the personal financialmanagement and bill payment system that are payor customers of businessusers of the business invoicing system; identifying a payor user of thepersonal financial management and bill payment system that is a payorcustomer of a payee business user of the business invoicing system;designating the payor user of the personal financial management and billpayment system first payor user of the personal financial management andbill payment system; providing first payor user of the personalfinancial management and bill payment system the opportunity tointegrate invoices generated by the first payee business user of thebusiness invoicing system into the personal financial management andbill payment system; and if the first payor user of the personalfinancial management and bill payment system agrees to integrateinvoices generated by the first payee business user of the businessinvoicing system into the personal financial management and bill paymentsystem, providing the first payee business user of the businessinvoicing system the capability to provide invoice data representinginvoices generated by the first payee business user of the businessinvoicing system to the first payor user of the personal financialmanagement and bill payment system through the personal financialmanagement and bill payment system.
 5. The method for integratingdiscrete invoices into a personal financial management and bill paymentsystem and then aggregating discrete invoices having the same payeebusiness into a single funds transfer transaction of claim 1 wherein thepersonal financial management and bill payment system is a financialtransaction management and billing system through which a user of thefinancial transaction management and billing system is provided thecapability to categorize financial transactions and pay the user'sbills.
 6. The method for integrating discrete invoices into a personalfinancial management and bill payment system and then aggregatingdiscrete invoices having the same payee business into a single fundstransfer transaction of claim 1 wherein integrating the invoice relatedfinancial transaction data into personal financial management and billpayment system payment due data associated with a personal financialmanagement and bill payment system includes assigning a personalfinancial management and bill payment system financial transactioncategory to the discrete invoices represented in the invoice relatedfinancial transaction data.
 7. The method for integrating discreteinvoices into a personal financial management and bill payment systemand then aggregating discrete invoices having the same payee businessinto a single funds transfer transaction of claim 1 wherein integratingthe invoice related financial transaction data into personal financialmanagement and bill payment system payment due data associated with apersonal financial management and bill payment system includes providingthe discrete invoices represented in the invoice related financialtransaction data as line items in a payment due item listing generatedthrough the personal financial management and bill payment system. 8.The method for integrating discrete invoices into a personal financialmanagement and bill payment system and then aggregating discreteinvoices having the same payee business into a single funds transfertransaction of claim 1 wherein processing the aggregated total firstpayee business invoice payment amount data a as a single first payeebusiness funds transfer item using the personal financial management andbill payment system includes providing aggregated total first payeebusiness invoice payment amount data as a funds transfer transactionitem in a funds transfer transaction item listing generated through thepersonal financial management and bill payment system.
 9. The method forintegrating discrete invoices into a personal financial management andbill payment system and then aggregating discrete invoices having thesame payee business into a single funds transfer transaction of claim 1wherein processing the aggregated total first payee business invoicepayment amount data as a single first payee business funds transfer itemusing the personal financial management and bill payment system includesapplying one or more aggregated first payee business invoice paymentrequest invoice data processing rules to the aggregated total firstpayee business invoice payment amount data.
 10. The method forintegrating discrete invoices into a personal financial management andbill payment system and then aggregating discrete invoices having thesame payee business into a single funds transfer transaction of claim 9wherein the aggregated first payee business invoice payment requestinvoice data processing rules include one or more of: an aggregatedfirst payee business invoice payment request invoice data processingrule limiting the aggregated total first payee business invoice paymentamount data to a threshold amount; and an aggregated first payeebusiness invoice payment request invoice data processing rule limitingthe total number of discrete invoice payment request related invoicesrepresented in the aggregated first payee business invoice paymentrequest invoice data to a threshold number of discrete invoices.
 11. Asystem for integrating discrete invoices into a personal financialmanagement and bill payment system and then aggregating discreteinvoices having the same payee business into a single funds transfertransaction comprising: an invoice related financial transaction dataacquisition module for obtaining access to invoice related financialtransaction data generated by the one or more payee businesses, theinvoice related financial transaction data representing two or morediscrete invoices submitted by one or more payee businesses requestingpayment by one or more payor users of the personal financial managementand bill payment system, the invoice related financial transaction dataincluding: payee business identity data associated with each discreteinvoice represented in the invoice related financial transaction data,the payee business identity data representing the identity of the payeebusiness associated with each discrete invoice represented in theinvoice related financial transaction data, payor user identity dataassociated with each discrete invoice represented in the invoice relatedfinancial transaction data, the payor user identity data representingthe identity of the payor user associated with each discrete invoicerepresented in the invoice related financial transaction data; andinvoice amount data associated with each discrete invoice represented inthe invoice related financial transaction data, the invoice amount datarepresenting the payment amount associated with each discrete invoicerepresented in the invoice related financial transaction data; anintegration module for integrating the invoice related financialtransaction data into personal financial management and bill paymentsystem payment due data associated with a personal financial managementand bill payment system, the personal financial management and billpayment system payment due data representing one or more billsassociated with one or more users of the personal financial managementand bill payment system to be paid through the personal financialmanagement and bill payment system; an invoice payment request datareceiving module for receiving invoice payment request data from one ormore users of the personal financial management and bill payment system,the invoice payment request data representing one or more requests fromone or more users of the personal financial management and bill paymentsystem to pay one or more requested invoice payment amounts associatedwith one or more discrete invoice payment request related invoicesrepresented in the invoice related financial transaction data throughthe personal financial management and bill payment system; a personalfinancial management and bill payment system access module for obtainingaccess to the personal financial management and bill payment system andpersonal financial management and bill payment system payment due data,including the integrated invoice related financial transaction data, andthe invoice payment request data; a discrete invoice payment requestrelated invoice data identification module for analyzing the invoicepayment request data to identify discrete invoice payment requestrelated invoice data representing one or more discrete invoice paymentrequest related invoices represented in the invoice related financialtransaction data; a payee business identity data identification modulefor analyzing the integrated invoice related financial transaction dataassociated with the discrete invoice payment request related invoices toidentify the payee business identity data associated with each discreteinvoice payment request related invoice represented in the discreteinvoice payment request related invoice data and identifying a firstpayee business represented in the payee business identity dataassociated with two or more discrete first payee business invoicepayment request related invoices represented in the discrete invoicepayment request related invoice data; an invoice related financialtransaction data aggregation module for aggregating all the invoicerelated financial transaction data associated with the two or morediscrete invoice payment request related invoices to generate aggregatedfirst payee business invoice payment request invoice data; an invoiceamount data identification module for analyzing the aggregated firstpayee business invoice payment request invoice data to identify therequested invoice payment amount data associated with each of the two ormore discrete invoice payment request related invoices; an aggregatedtotal first payee business invoice payment amount data calculationmodule for adding the requested invoice payment amount data associatedwith each of the two or more discrete invoice payment request relatedinvoices to generate aggregated total first payee business invoicepayment amount data representing a total requested invoice paymentamount for the first payee business requested by two or more users ofthe personal financial management and bill payment system; and anaggregated total first payee business invoice payment amount dataprocessing module for processing the aggregated total first payeebusiness invoice payment amount data as a single first payee businessfunds transfer item using the personal financial management and billpayment system.
 12. The system for integrating discrete invoices into apersonal financial management and bill payment system and thenaggregating discrete invoices having the same payee business into asingle funds transfer transaction of claim 11 wherein obtaining accessto invoice related financial transaction data generated by the one ormore payee businesses includes: obtaining access to personal financialmanagement and bill payment system user financial transaction dataassociated with the personal financial management and bill paymentsystem, the personal financial management and bill payment system userfinancial transaction data representing financial transactionsassociated with users of a personal financial management and billpayment system; analyzing the personal financial management and billpayment system user financial transaction data associated with the firstpayor user to identify payee data included in the financial transactiondata associated with a first payor user, the payee data representing oneor more payees associated with first payor user financial transactionsassociated with the first payor user represented by a portion of thepersonal financial management and bill payment system user financialtransaction data associated with the first payor user; obtaining accessto business invoicing system business user identification dataassociated with a business invoicing system, the business useridentification data representing business users of the businessinvoicing system; accessing the payee data and the business useridentification data and analyzing the payee data and business useridentification data to determine if a payee represented in the payeedata matches a business user of the business invoicing systemrepresented in the business user identification data; identifying apayee represented in the payee data that matches a business user of thebusiness invoicing system represented in the business useridentification data, the payee being a payee associated with firstfinancial transaction data representing a first financial transactionincluded in the personal financial management and bill payment systemuser financial transaction data associated with the first payor user;designating the payee represented in the payee data that matches thebusiness user of the business invoicing system as a first payeebusiness; transforming status data associated with the first financialtransaction data representing the first financial transaction to firstinvoice related financial transaction data; processing the first invoicerelated financial transaction data as invoice related financialtransaction data; and providing the first payee business the capabilityto provide invoicing data representing invoices generated by first payeebusiness to the first payor user of the personal financial managementand bill payment system through the personal financial management andbill payment system.
 13. The system for integrating discrete invoicesinto a personal financial management and bill payment system and thenaggregating discrete invoices having the same payee business into asingle funds transfer transaction of claim 11 wherein obtaining accessto invoice related financial transaction data generated by the one ormore payee businesses includes: obtaining access to personal financialmanagement and bill payment system user identification data associatedwith users of a personal financial management and bill payment system;obtaining access to invoicing data generated through a businessinvoicing system, the invoicing data representing invoices sent frompayee business users of the business invoicing system to payor customersof the payee business users of the business invoicing system; monitoringthe invoicing data and identifying first invoice data representing aninvoice generated by a first payee business user of the businessinvoicing system associated with a first payor customer of the firstpayee business user of the business invoicing system; analyzing thefirst invoice data to identify first payor customer identification dataassociated with the first payor customer of the first payee businessuser of the business invoicing system; analyzing the personal financialmanagement and bill payment system user identification data and thefirst payor customer identification data to determine if the first payorcustomer associated with the first payor customer identification data isa first payor user of the personal financial management and bill paymentsystem; if a determination is made that the first payor customerassociated with the first payor customer identification data is a firstpayor user of the personal financial management and bill payment system,designating the first payor customer as a first payor user of thepersonal financial management and bill payment system; and providing thefirst payee business user of the business invoicing system thecapability to provide invoicing data representing invoices generated bythe first payee business user of the business invoicing system to thefirst payor user of the personal financial management and bill paymentsystem through the personal financial management and bill paymentsystem.
 14. The system for integrating discrete invoices into a personalfinancial management and bill payment system and then aggregatingdiscrete invoices having the same payee business into a single fundstransfer transaction of claim 11 wherein obtaining access to invoicerelated financial transaction data generated by the one or more payeebusinesses includes: obtaining access to personal financial managementand bill payment system user identification data associated with usersof a personal financial management and bill payment system; obtainingaccess to business invoicing system payor customer identification datagenerated through a business invoicing system, the business invoicingsystem payor customer identification data being associated with payorcustomers of user payee businesses of a business invoicing system;analyzing the personal financial management and bill payment system useridentification data and the business invoicing system payor customeridentification data to identify payor users of the personal financialmanagement and bill payment system that are payor customers of businessusers of the business invoicing system; identifying a payor user of thepersonal financial management and bill payment system that is a payorcustomer of a payee business user of the business invoicing system;designating the payor user of the personal financial management and billpayment system first payor user of the personal financial management andbill payment system; providing first payor user of the personalfinancial management and bill payment system the opportunity tointegrate invoices generated by the first payee business user of thebusiness invoicing system into the personal financial management andbill payment system; and if the first payor user of the personalfinancial management and bill payment system agrees to integrateinvoices generated by the first payee business user of the businessinvoicing system into the personal financial management and bill paymentsystem, providing the first payee business user of the businessinvoicing system the capability to provide invoice data representinginvoices generated by the first payee business user of the businessinvoicing system to the first payor user of the personal financialmanagement and bill payment system through the personal financialmanagement and bill payment system.
 15. The system for integratingdiscrete invoices into a personal financial management and bill paymentsystem and then aggregating discrete invoices having the same payeebusiness into a single funds transfer transaction of claim 11 whereinthe personal financial management and bill payment system is a financialtransaction management and billing system through which a user of thefinancial transaction management and billing system is provided thecapability to categorize financial transactions and pay the user'sbills.
 16. The system for integrating discrete invoices into a personalfinancial management and bill payment system and then aggregatingdiscrete invoices having the same payee business into a single fundstransfer transaction of claim 11 wherein integrating the invoice relatedfinancial transaction data into personal financial management and billpayment system payment due data associated with a personal financialmanagement and bill payment system includes assigning a personalfinancial management and bill payment system financial transactioncategory to the discrete invoices represented in the invoice relatedfinancial transaction data.
 17. The system for integrating discreteinvoices into a personal financial management and bill payment systemand then aggregating discrete invoices having the same payee businessinto a single funds transfer transaction of claim 11 wherein integratingthe invoice related financial transaction data into personal financialmanagement and bill payment system payment due data associated with apersonal financial management and bill payment system includes providingthe discrete invoices represented in the invoice related financialtransaction data as line items in a payment due item listing generatedthrough the personal financial management and bill payment system. 18.The system for integrating discrete invoices into a personal financialmanagement and bill payment system and then aggregating discreteinvoices having the same payee business into a single funds transfertransaction of claim 11 wherein processing the aggregated total firstpayee business invoice payment amount data a as a single first payeebusiness funds transfer item using the personal financial management andbill payment system includes providing aggregated total first payeebusiness invoice payment amount data as a funds transfer transactionitem in a funds transfer transaction item listing generated through thepersonal financial management and bill payment system.
 19. The systemfor integrating discrete invoices into a personal financial managementand bill payment system and then aggregating discrete invoices havingthe same payee business into a single funds transfer transaction ofclaim 11 wherein processing the aggregated total first payee businessinvoice payment amount data as a single first payee business fundstransfer item using the personal financial management and bill paymentsystem includes applying one or more aggregated first payee businessinvoice payment request invoice data processing rules to the aggregatedtotal first payee business invoice payment amount data.
 20. The systemfor integrating discrete invoices into a personal financial managementand bill payment system and then aggregating discrete invoices havingthe same payee business into a single funds transfer transaction ofclaim 19 wherein the aggregated first payee business invoice paymentrequest invoice data processing rules include one or more of: anaggregated first payee business invoice payment request invoice dataprocessing rule limiting the aggregated total first payee businessinvoice payment amount data to a threshold amount; and an aggregatedfirst payee business invoice payment request invoice data processingrule limiting the total number of discrete invoice payment requestrelated invoices represented in the aggregated first payee businessinvoice payment request invoice data to a threshold number of discreteinvoices.
 21. A computer program product for integrating discreteinvoices into a personal financial management and bill payment systemand then aggregating discrete invoices having the same payee businessinto a single funds transfer transaction, the computer program productincluding machine readable instructions for implementing a process forintegrating discrete invoices into a personal financial management andbill payment system and then aggregating discrete invoices having thesame payee business into a single funds transfer transaction, theprocess for integrating discrete invoices into a personal financialmanagement and bill payment system and then aggregating discreteinvoices having the same payee business into a single funds transfertransaction comprising: obtaining access to invoice related financialtransaction data generated by the one or more payee businesses, theinvoice related financial transaction data representing two or morediscrete invoices submitted by one or more payee businesses requestingpayment by one or more payor users of the personal financial managementand bill payment system, the invoice related financial transaction dataincluding: payee business identity data associated with each discreteinvoice represented in the invoice related financial transaction data,the payee business identity data representing the identity of the payeebusiness associated with each discrete invoice represented in theinvoice related financial transaction data; payor user identity dataassociated with each discrete invoice represented in the invoice relatedfinancial transaction data, the payor user identity data representingthe identity of the payor user associated with each discrete invoicerepresented in the invoice related financial transaction data; andinvoice amount data associated with each discrete invoice represented inthe invoice related financial transaction data, the invoice amount datarepresenting the payment amount associated with each discrete invoicerepresented in the invoice related financial transaction data;integrating the invoice related financial transaction data into personalfinancial management and bill payment system payment due data associatedwith a personal financial management and bill payment system, thepersonal financial management and bill payment system payment due datarepresenting one or more bills associated with one or more users of thepersonal financial management and bill payment system to be paid throughthe personal financial management and bill payment system; receivinginvoice payment request data from one or more users of the personalfinancial management and bill payment system, the invoice paymentrequest data representing one or more requests from one or more users ofthe personal financial management and bill payment system to pay one ormore requested invoice payment amounts associated with one or morediscrete invoice payment request related invoices represented in theinvoice related financial transaction data through the personalfinancial management and bill payment system; obtaining access to thepersonal financial management and bill payment system; obtaining accessto the personal financial management and bill payment system payment duedata, including the integrated invoice related financial transactiondata; obtaining access to the invoice payment request data; analyzingthe invoice payment request data to identify discrete invoice paymentrequest related invoice data representing one or more discrete invoicepayment request related invoices represented in the invoice relatedfinancial transaction data; analyzing the integrated invoice relatedfinancial transaction data associated with the discrete invoice paymentrequest related invoices to identify the payee business identity dataassociated with each discrete invoice payment request related invoicerepresented in the discrete invoice payment request related invoicedata; identifying a first payee business represented in the payeebusiness identity data associated with two or more discrete first payeebusiness invoice payment request related invoices represented in thediscrete invoice payment request related invoice data; aggregating allthe invoice related financial transaction data associated with the twoor more discrete invoice payment request related invoices to generateaggregated first payee business invoice payment request invoice data;analyzing the aggregated first payee business invoice payment requestinvoice data to identify the requested invoice payment amount dataassociated with each of the two or more discrete invoice payment requestrelated invoices; adding the requested invoice payment amount dataassociated with each of the two or more discrete invoice payment requestrelated invoices to generate aggregated total first payee businessinvoice payment amount data representing a total requested invoicepayment amount for the first payee business requested by two or moreusers of the personal financial management and bill payment system; andprocessing the aggregated total first payee business invoice paymentamount data as a single first payee business funds transfer item usingthe personal financial management and bill payment system.
 22. Thecomputer program product for integrating discrete invoices into apersonal financial management and bill payment system and thenaggregating discrete invoices having the same payee business into asingle funds transfer transaction of claim 21 wherein obtaining accessto invoice related financial transaction data generated by the one ormore payee businesses includes: obtaining access to personal financialmanagement and bill payment system user financial transaction dataassociated with the personal financial management and bill paymentsystem, the personal financial management and bill payment system userfinancial transaction data representing financial transactionsassociated with users of a personal financial management and billpayment system; analyzing the personal financial management and billpayment system user financial transaction data associated with the firstpayor user to identify payee data included in the financial transactiondata associated with a first payor user, the payee data representing oneor more payees associated with first payor user financial transactionsassociated with the first payor user represented by a portion of thepersonal financial management and bill payment system user financialtransaction data associated with the first payor user; obtaining accessto business invoicing system business user identification dataassociated with a business invoicing system, the business useridentification data representing business users of the businessinvoicing system; accessing the payee data and the business useridentification data and analyzing the payee data and business useridentification data to determine if a payee represented in the payeedata matches a business user of the business invoicing systemrepresented in the business user identification data; identifying apayee represented in the payee data that matches a business user of thebusiness invoicing system represented in the business useridentification data, the payee being a payee associated with firstfinancial transaction data representing a first financial transactionincluded in the personal financial management and bill payment systemuser financial transaction data associated with the first payor user;designating the payee represented in the payee data that matches thebusiness user of the business invoicing system as a first payeebusiness; transforming status data associated with the first financialtransaction data representing the first financial transaction to firstinvoice related financial transaction data; processing the first invoicerelated financial transaction data as invoice related financialtransaction data; and providing the first payee business the capabilityto provide invoicing data representing invoices generated by first payeebusiness to the first payor user of the personal financial managementand bill payment system through the personal financial management andbill payment system.
 23. The computer program product for integratingdiscrete invoices into a personal financial management and bill paymentsystem and then aggregating discrete invoices having the same payeebusiness into a single funds transfer transaction of claim 21 whereinobtaining access to invoice related financial transaction data generatedby the one or more payee businesses includes: obtaining access topersonal financial management and bill payment system useridentification data associated with users of a personal financialmanagement and bill payment system; obtaining access to invoicing datagenerated through a business invoicing system, the invoicing datarepresenting invoices sent from payee business users of the businessinvoicing system to payor customers of the payee business users of thebusiness invoicing system; monitoring the invoicing data and identifyingfirst invoice data representing an invoice generated by a first payeebusiness user of the business invoicing system associated with a firstpayor customer of the first payee business user of the businessinvoicing system; analyzing the first invoice data to identify firstpayor customer identification data associated with the first payorcustomer of the first payee business user of the business invoicingsystem; analyzing the personal financial management and bill paymentsystem user identification data and the first payor customeridentification data to determine if the first payor customer associatedwith the first payor customer identification data is a first payor userof the personal financial management and bill payment system; and if adetermination is made that the first payor customer associated with thefirst payor customer identification data is a first payor user of thepersonal financial management and bill payment system, designating thefirst payor customer as a first payor user of the personal financialmanagement and bill payment system; providing the first payee businessuser of the business invoicing system the capability to provideinvoicing data representing invoices generated by the first payeebusiness user of the business invoicing system to the first payor userof the personal financial management and bill payment system through thepersonal financial management and bill payment system.
 24. The computerprogram product for integrating discrete invoices into a personalfinancial management and bill payment system and then aggregatingdiscrete invoices having the same payee business into a single fundstransfer transaction of claim 21 wherein obtaining access to invoicerelated financial transaction data generated by the one or more payeebusinesses includes: obtaining access to personal financial managementand bill payment system user identification data associated with usersof a personal financial management and bill payment system; obtainingaccess to business invoicing system payor customer identification datagenerated through a business invoicing system, the business invoicingsystem payor customer identification data being associated with payorcustomers of user payee businesses of a business invoicing system;analyzing the personal financial management and bill payment system useridentification data and the business invoicing system payor customeridentification data to identify payor users of the personal financialmanagement and bill payment system that are payor customers of businessusers of the business invoicing system; identifying a payor user of thepersonal financial management and bill payment system that is a payorcustomer of a payee business user of the business invoicing system;designating the payor user of the personal financial management and billpayment system first payor user of the personal financial management andbill payment system; providing first payor user of the personalfinancial management and bill payment system the opportunity tointegrate invoices generated by the first payee business user of thebusiness invoicing system into the personal financial management andbill payment system; and if the first payor user of the personalfinancial management and bill payment system agrees to integrateinvoices generated by the first payee business user of the businessinvoicing system into the personal financial management and bill paymentsystem, providing the first payee business user of the businessinvoicing system the capability to provide invoice data representinginvoices generated by the first payee business user of the businessinvoicing system to the first payor user of the personal financialmanagement and bill payment system through the personal financialmanagement and bill payment system.
 25. The computer program product forintegrating discrete invoices into a personal financial management andbill payment system and then aggregating discrete invoices having thesame payee business into a single funds transfer transaction of claim 21wherein the personal financial management and bill payment system is afinancial transaction management and billing system through which a userof the financial transaction management and billing system is providedthe capability to categorize financial transactions and pay the user'sbills.
 26. The computer program product for integrating discreteinvoices into a personal financial management and bill payment systemand then aggregating discrete invoices having the same payee businessinto a single funds transfer transaction of claim 21 wherein integratingthe invoice related financial transaction data into personal financialmanagement and bill payment system payment due data associated with apersonal financial management and bill payment system includes assigninga personal financial management and bill payment system financialtransaction category to the discrete invoices represented in the invoicerelated financial transaction data.
 27. The computer program product forintegrating discrete invoices into a personal financial management andbill payment system and then aggregating discrete invoices having thesame payee business into a single funds transfer transaction of claim 21wherein integrating the invoice related financial transaction data intopersonal financial management and bill payment system payment due dataassociated with a personal financial management and bill payment systemincludes providing the discrete invoices represented in the invoicerelated financial transaction data as line items in a payment due itemlisting generated through the personal financial management and billpayment system.
 28. The computer program product for integratingdiscrete invoices into a personal financial management and bill paymentsystem and then aggregating discrete invoices having the same payeebusiness into a single funds transfer transaction of claim 21 whereinprocessing the aggregated total first payee business invoice paymentamount data a as a single first payee business funds transfer item usingthe personal financial management and bill payment system includesproviding aggregated total first payee business invoice payment amountdata as a funds transfer transaction item in a funds transfertransaction item listing generated through the personal financialmanagement and bill payment system.
 29. The computer program product forintegrating discrete invoices into a personal financial management andbill payment system and then aggregating discrete invoices having thesame payee business into a single funds transfer transaction of claim 21wherein processing the aggregated total first payee business invoicepayment amount data as a single first payee business funds transfer itemusing the personal financial management and bill payment system includesapplying one or more aggregated first payee business invoice paymentrequest invoice data processing rules to the aggregated total firstpayee business invoice payment amount data.
 30. The computer programproduct for integrating discrete invoices into a personal financialmanagement and bill payment system and then aggregating discreteinvoices having the same payee business into a single funds transfertransaction of claim 29 wherein the aggregated first payee businessinvoice payment request invoice data processing rules include one ormore of: an aggregated first payee business invoice payment requestinvoice data processing rule limiting the aggregated total first payeebusiness invoice payment amount data to a threshold amount; and anaggregated first payee business invoice payment request invoice dataprocessing rule limiting the total number of discrete invoice paymentrequest related invoices represented in the aggregated first payeebusiness invoice payment request invoice data to a threshold number ofdiscrete invoices.